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 commands/jayminwest/burrow/releasegit clone --depth 1 https://github.com/jayminwest/burrowWhat 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.00001 | $0.00214 |
| Opus 5 | $0.00000 | $0.00107 |
| Sonnet 5 | $0.00000 | $0.00043 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
release 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 2d 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.
This is a copy
100% identical to release — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
body
Analyze all changes since the last release and prepare a new version.
Steps:
- Find the last release tag:
git describe --tags --abbrev=0 2>/dev/null || echo "none" - If there's a previous tag, review changes:
git log <tag>..HEAD --onelineandgit diff <tag>..HEAD - Determine the version bump level. Always use patch unless the user explicitly requests minor or major.
- Bump version in both
package.jsonandsrc/index.tsusingbun run version:bump <level> - Update
CHANGELOG.md— move items from [Unreleased] to the new version section with today's date - Update
CLAUDE.mdif command counts or structure changed - Update
README.mdif CLI reference or stats changed - Commit all changes with a message like "release: vX.Y.Z". Then present a summary of what changed.
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.
- 2d ago First seen · 19 lines · 1 tokens per session scan A feab4c1e57a8
release is a command published in the GitHub repository jayminwest/burrow (11 stars, last pushed 1mo ago), licensed MIT. It adds 1 tokens to every session and 214 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to release, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
ship
Commit all changes, push branch, create/update PR, and run local validation.
release
Prepare a new release for sandvault. This command updates the changelog, bumps the version, and creates a PR.
review-pr
Perform a comprehensive code review using subagents for key areas.
label-issue
Apply labels to GitHub issues.
release-notes
Curate a CHANGELOG.md entry from commits since the last release; with a bump arg, also version, commit, and push the tag — then hand the npm publish to the user (they publish manually). nightly instead cuts a pre-release from the nightly branch. Also flags when the separately-published provider SDK needs a republish.
defensive-code-cleanup
Clean Defensive Try-Catch Blocks.