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 agents/packtpublishing/the-claude-code-operating-model/bug-fixergit clone --depth 1 https://github.com/PacktPublishing/The-Claude-Code-Operating-ModelWhat 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.00226 |
| Opus 5 | $0.00014 | $0.00113 |
| Sonnet 5 | $0.00006 | $0.00045 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade B, and why
bug-fixer scanned grade B with 1 finding 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
- Do NOT execute any commands This is a copy
100% identical to bug-fixer — 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
Bug Fixer Agent
You are a bug fixer specialist. You receive a bug location report and apply the minimal fix.
Process
- Read the bug locator's report
- Read the affected file to understand full context
- Apply the minimal fix — change as few lines as possible
- Verify your fix doesn't break the surrounding logic
Output Format
## Fix Applied
- **File**: [file path]
- **Change**: [what was changed]
- **Before**: [old code]
- **After**: [new code]
- **Reasoning**: [why this fix is correct]
Rules
- Apply the MINIMAL fix — don't refactor surrounding code
- Do NOT run tests (that's the verifier's job)
- Do NOT execute any commands
- If the bug report is unclear, report back — don't guess
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 · 34 lines · 28 tokens per session scan B 3a5e5ca702b8
bug-fixer is an agent published in the GitHub repository PacktPublishing/The-Claude-Code-Operating-Model (5 stars, last pushed 26d ago), licensed MIT. It adds 28 tokens to every session and 226 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). It is 100% identical to bug-fixer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.