Sandbox Check

Sandbox audit that probes, from inside a live coding-agent session, what the agent can really reach: secret files it can open, secret-like environment variables, files that git, the shell, the editor, or the harness later run (git hooks, shell startup files, harness settings), writes outside the project, the Docker socket, the SSH agent, and passwordless sudo. Use when the user asks what the agent can access or write on this machine, whether the sandbox actually works, how big the blast radius is if the agent gets prompt-injected, whether SSH keys, cloud credentials, or .env files are exposed, or whether it could escape through Docker or sudo. Runs locally and edits no existing file: it creates and deletes one empty test file per folder it checks, and only the optional --network flag makes DNS lookups and TCP connections.

RyanAlberts Updated 9 repo stars
Autonomy × Recovery — every loop-owning project placed by designed autonomy regime and failure-recovery tier

File contents

RyanAlberts/best-of-Agent-Harnesses commit eb45edfd28

Frequently asked questions

npx get-skill add ryanalberts/sandbox-check