Agent Safehouse is a macOS sandboxing tool that restricts local AI coding agents to the files and integrations they are allowed to use. It is for developers who want to reduce the damage an agent can cause while preserving normal development workflows. Its catalogue entries help configure or use the sandbox with coding agents.
Borrowing it
Nothing to install: this file belongs to eugene1g/agent-safehouse. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/eugene1g/agent-safehouse/main/AGENTS.mdgit clone --depth 1 https://github.com/eugene1g/agent-safehouseWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/eugene1g/agent-safehouse/agents-md)<a href="https://agentmods.dev/instructions/eugene1g/agent-safehouse/agents-md"><img src="https://agentmods.dev/badge/instructions/eugene1g/agent-safehouse/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/eugene1g/agent-safehouse/agents-md"><img src="https://agentmods.dev/badge/instructions/eugene1g/agent-safehouse/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.01346 | $0.01346 |
| Opus 5.5 | $0.00538 | $0.00538 |
| Sonnet 5.5 | $0.00269 | $0.00269 |
| Haiku 4.5 | $0.00135 | $0.00135 |
Grade A, and why
agent-safehouse AGENTS.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Safehouse: LLM Quick Reference
What This Project Is
Agent Safehouse is a macOS sandbox wrapper for coding agents (Claude, Cursor, Aider, Gemini, etc.) built on sandbox-exec.
Policy model is strict by default: start from (deny default), then add explicit allow rules via layered .sb profiles.
Core sandbox wrapper is pure Bash + Sandbox Profile Language (.sb) and has no build step. Repo also includes a VitePress docs site and Cloudflare deploy tooling (pnpm + Wrangler).
Fast Working Rules
- Use
rgfor text search. - Use
fdfor file listing/find. - Make least-privilege policy edits; avoid broad
subpathgrants unless required. - Do not hand-edit
dist/*; editbin/andprofiles/, then regenerate dist artifacts. - If you change any
.sbfile or policy assembly/runtime logic (bin/safehouse.sh,bin/lib/*.sh), run./scripts/generate-dist.sh. - Run tests with
./tests/run.shon macOS withsandbox-exec, outside any existing sandbox. Use./tests/run.sh e2efor the tmux-driven startup/prompt-roundtrip suite for agent TUIs. - If tests cannot run because the current session is already sandboxed, state that explicitly and continue with static validation.
Core Commands
# Generate policy only (prints temp policy path)
./bin/safehouse.sh [--add-dirs-ro=...] [--add-dirs=...] [--enable=...] [--append-profile=...]
# Run command in sandbox
./bin/safehouse.sh [policy opts] -- <command> [args...]
./bin/safehouse.sh --stdout
# Explain effective workdir/grants/profile selection (debugging)
./bin/safehouse.sh --explain --stdout
# Trust and load <workdir>/.safehouse config (disabled by default)
./bin/safehouse.sh --trust-workdir-config --stdout
# Validate behavior
./tests/run.sh
./tests/run.sh e2e
# Regenerate committed dist artifacts
./scripts/generate-dist.sh
./scripts/generate-dist.sh updates these deterministic outputs:
dist/safehouse.sh
Dist Purpose
dist/ is for consumers: it provides ready-to-run packaged artifacts, especially dist/safehouse.sh, a single executable containing the assembled policy + runtime shell logic.
Authoring source of truth is bin/ and profiles/; make functional changes there, then regenerate dist/.
Agents should usually avoid loading dist/ files into context unless validating generated distribution output or debugging packaging/compression regressions.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago Changed · -4 tokens per session 87ab41a296e0
- 1mo ago First seen · 98 lines · 1,350 tokens per session scan A d2988c15c670
agent-safehouse AGENTS.md is an instructions file published in the GitHub repository eugene1g/agent-safehouse (2,121 stars, last pushed 6d ago), licensed Apache-2.0. It adds 1,346 tokens to every session, about $0.0054 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.