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/agent-anatomy/claude/prgit clone --depth 1 https://github.com/agent-anatomy/claudeWhat 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.00008 | $0.00256 |
| Opus 5 | $0.00004 | $0.00128 |
| Sonnet 5 | $0.00002 | $0.00051 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
pr 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.
What it actually says
Create a pull request for the current branch.
Steps
- Run
git log main..HEAD— understand what commits are included - Run
git diff main..HEAD— read all the changes - Draft a PR title (under 70 characters, imperative mood)
- Write a PR body with:
- What changed and why
- Any important implementation decisions
- How to test it manually
- Run
gh pr createwith the title and body
PR title rules
- Imperative mood: "Add X", "Fix Y", "Remove Z"
- Under 70 characters
- No issue numbers in the title (put them in the body)
PR body format
## What
[1-3 sentences on what changed]
## Why
[The motivation — bug, feature request, tech debt]
## Test plan
- [ ] [Manual step to verify it works]
- [ ] [Edge case to check]
What NOT to do
- No AI attribution in the PR body
- No listing every file changed
- No "as per your request" or similar filler
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 · 39 lines · 8 tokens per session scan A eaaa3bd5d37b
pr is a command published in the GitHub repository agent-anatomy/claude (2 stars, last pushed 4mo ago), licensed MIT. It adds 8 tokens to every session and 256 once invoked, about $0.0000 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-31.
Other commands, from other repositories
create-pr
Create a pull request following the official template.
review-code
Read ALL memory bank code rules + best practices, check the files that changed, and APPLY fixes so they adhere. The active counterpart to /scan (which is read-only). Use after an AI session, before commit, to make changed files compliant.
learn
Command "learn" from chohra-med/expo_boilerplate, covering command: learn — the learning loop (feedback → rules), when to run it, invocation, the loop (6 steps) and 1 — capture.
migrate
Command "migrate" from chohra-med/expo_boilerplate, covering invocation, steps and rule.
audit
Command "audit" from chohra-med/expo_boilerplate, covering invocation, checks and output.
build
Command "build" from chohra-med/expo_boilerplate, covering command: build — run the sdd pipeline over tasks.md, invocation, per-task cycle, gates (constitution) and output.