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/dbc-oduffy/coordinator-claude/bug-blitzgit clone --depth 1 https://github.com/dbc-oduffy/coordinator-claudeWrote 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/dbc-oduffy/coordinator-claude/bug-blitz)<a href="https://agentmods.dev/commands/dbc-oduffy/coordinator-claude/bug-blitz"><img src="https://agentmods.dev/badge/commands/dbc-oduffy/coordinator-claude/bug-blitz.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.00021 | $0.02717 |
| Opus 5 | $0.00010 | $0.01358 |
| Sonnet 5 | $0.00004 | $0.00543 |
| Haiku 4.5 | $0.00002 | $0.00272 |
Grade A, and why
bug-blitz 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 yesterday.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- yesterday Changed · +13 lines bdc64f9e0444
- 4d ago First seen · 163 lines · 21 tokens per session scan A 0a4656f02e94
bug-blitz is a command published in the GitHub repository dbc-oduffy/coordinator-claude (5 stars, last pushed 2d ago), with no licence file. It adds 21 tokens to every session and 2,717 once invoked, about $0.0001 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
develop
Implement skill development issues with TDD-governed workflow.
write
Launch a writing-mode agent team.
app-init
Start a new mobile app project — runs requirements intake, then CEO vision, then PRD + architecture in parallel.
bug
Reproduce then TDD-fix a ready-for-agent bug ticket in this checkout. Web bugs get a browser repro first.
app-status
Show the current state of the project — vision, sprint goal, board, blockers, daily report.
init
Initialize agent-harness model routing for your Claude tier (subscription or API).