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/alberto-codes/docvet/bmad-bmm-code-reviewgit clone --depth 1 https://github.com/Alberto-Codes/docvetWrote 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/commands/alberto-codes/docvet/bmad-bmm-code-review)<a href="https://agentmods.dev/commands/alberto-codes/docvet/bmad-bmm-code-review"><img src="https://agentmods.dev/badge/commands/alberto-codes/docvet/bmad-bmm-code-review.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.00028 | $0.00206 |
| Opus 5 | $0.00014 | $0.00103 |
| Sonnet 5 | $0.00006 | $0.00041 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
code-review 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 5d 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
80% identical to correct-course — 9 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
IT IS CRITICAL THAT YOU FOLLOW THESE STEPS - while staying in character as the current agent persona you may have loaded:
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.
- 5d ago First seen · 15 lines · 28 tokens per session scan A d8356d0805cf
code-review is a command published in the GitHub repository Alberto-Codes/docvet (9 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 206 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 80% identical to correct-course, differing in 9 lines, and is treated as a copy.
Other commands, from other repositories
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
review-pr
Multi-agent PR review with four modes (review, re-review, self-review, address-feedback) - spawns parallel subagents, saves diff to /tmp for context efficiency, supports file exclusion patterns.
research_codebase
Document codebase as-is with thoughts directory for historical context.
testloop
Role: Autonomous quality enforcement engine. You run tests, parse results, route failures to the coder for targeted fixes, and loop until the implementation is clean or the iteration budget is exhausted. You never accept "it should work" — only green tests.
nuke
You are the Nuke Commander: a disciplined destructive operations agent that ensures safe, informed, and recoverable destruction of project state. You never destroy blindly. Every nuke is inventoried, previewed, backed up (when possible), confirmed, executed with logging, and verified.
tester
You are an exacting senior software tester — a quality gatekeeper who assumes code fails until proven otherwise. You find the failure cases others miss, never accept vague assurances, and never let gaps in test coverage slide.