Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/jayminwest/burrow/claude-mdgit clone --depth 1 https://github.com/jayminwest/burrowWrote 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/jayminwest/burrow/claude-md)<a href="https://agentmods.dev/instructions/jayminwest/burrow/claude-md"><img src="https://agentmods.dev/badge/instructions/jayminwest/burrow/claude-md.svg" alt="Measured on agentmods" 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 | $0.01605 | $0.01605 |
| Opus 5 | $0.00803 | $0.00803 |
| Sonnet 5 | $0.00321 | $0.00321 |
| Haiku 4.5 | $0.00161 | $0.00161 |
Grade A, and why
burrow CLAUDE.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 4d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Burrow
OS-isolated sandbox runtime for coding agents. SPEC.md is the frozen V1 design record; ROADMAP.md is the punch list of forward-looking items. New deferred decisions out of design discussions land in ROADMAP.md as R-NN items rather than as standalone informational seeds.
Tech Stack
- Runtime: Bun (runs TypeScript directly, no build step)
- Language: TypeScript with strict mode (
noUncheckedIndexedAccess, noany) - Linting: Biome (formatter + linter; lint script runs
--error-on-warnings, so warnings fail CI) - Storage: SQLite via
bun:sqlitefor session/event persistence - Sandbox primitives:
bwrap(Linux),sandbox-exec(macOS) — no Docker, no daemon
Build & Test Commands
bun test # Run all tests
bun test src/foo.test.ts # Run a single test file
bun run lint # biome check --error-on-warnings .
bun run typecheck # tsc --noEmit
Quality Gates
Run all three before committing — warnings count as failures:
bun test && bun run lint && bun run typecheck
CI runs the same trinity. Don't merge with lint warnings; promote to error in biome.json or fix at write time.
TypeScript Conventions
- Strict mode with
noUncheckedIndexedAccess— always handle possibleundefinedfrom indexing - No
any— useunknownand narrow, or define proper types - All shared types in
src/types.ts - Import with
.tsextensions - Tab indentation, 100-char line width (enforced by Biome)
Version Management
Version lives in two places (kept in sync by scripts/version-bump.ts and verified by the publish workflow):
package.json—"version"fieldsrc/index.ts—const VERSION = "X.Y.Z"
Bump via: bun run version:bump <major|minor|patch>
Session Completion Protocol
When ending a work session, complete ALL steps:
- File issues for remaining work:
sd create --title "..." - Run quality gates (if code changed):
bun test && bun run lint && bun run typecheck - Close finished issues:
sd close <id> - Push:
sd sync && git push - Verify:
git statusshows "up to date with origin"
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.
- 4d ago First seen · 151 lines · 1,605 tokens per session scan A b5e6410505b5
burrow CLAUDE.md is an instructions file published in the GitHub repository jayminwest/burrow (12 stars, last pushed 1mo ago), licensed MIT. It adds 1,605 tokens to every session, about $0.0080 per session on Opus 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
OpenSandbox AGENTS.md
AGENTS.md instructions for opensandbox-group/OpenSandbox, covering opensandbox agents, repository map, routing, working principles and guardrails.
microsandbox AGENTS.md
AGENTS.md instructions for superradcompany/microsandbox, covering agents.md, scope, project map, design principles and backward compatibility review.
agentos CLAUDE.md
Claude Code instructions for rivet-dev/agentos, covering agentos, boundaries, security model, sqlite schema ownership and runtime and registry.
OpenSandbox CLAUDE.md
Claude Code instructions for opensandbox-group/OpenSandbox: See AGENTS.md for all rules, routing, and conventions.
agent-safehouse AGENTS.md
AGENTS.md instructions for eugene1g/agent-safehouse, covering agent safehouse: llm quick reference, what this project is, fast working rules, core commands and generate policy only (prints temp policy path).
agent-sandbox AGENTS.md
AGENTS.md instructions for kubernetes-sigs/agent-sandbox, covering agents.md, project summary, repository layout, agent skills and build, test, lint.