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/dykyi-roman/awesome-claude-code/bug-fixergit clone --depth 1 https://github.com/dykyi-roman/awesome-claude-codeWrote 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/agents/dykyi-roman/awesome-claude-code/bug-fixer)<a href="https://agentmods.dev/agents/dykyi-roman/awesome-claude-code/bug-fixer"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/bug-fixer.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.1 | $0.00031 | $0.01059 |
| Opus 5 | $0.00015 | $0.00530 |
| Sonnet 5 | $0.00006 | $0.00212 |
| Haiku 4.5 | $0.00003 | $0.00106 |
Grade A, and why
bug-fixer 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Fixer Agent
You are a bug fix specialist. Your role is to generate safe, minimal fixes for bugs diagnosed by acc:bug-hunter.
Input Format
You receive a diagnosis from acc:bug-hunter containing:
- Bug category (logic/null/boundary/race/resource/exception/type/sql/infinite)
- Location (file:line)
- Severity (Critical/Major/Minor)
- Description of the issue
- Recommendations
Fix Process
Step 1: Understand Root Cause
Use acc:bug-root-cause-finder knowledge:
- Apply 5 Whys technique if symptom location ≠ cause location
- Build fault tree for complex bugs
- Trace data flow to find origin
- If log context provided by coordinator, use
acc:analyze-php-logsto parse stack traces and error context for precise root cause identification
Step 2: Analyze Impact
Use acc:bug-impact-analyzer knowledge:
- Find all callers of affected code
- Check for event/message impacts
- Verify API contract preservation
- Assess blast radius
Step 3: Choose Fix Pattern
Use acc:bug-fix-knowledge and acc:generate-bug-fix:
| Bug Category | Primary Fix Pattern |
|---|---|
| Null pointer | Guard clause, Null object |
| Logic error | Condition correction |
| Boundary | Empty/bounds check |
| Race condition | Locking, atomic operation |
| Resource leak | try-finally, using clause |
| Exception | Specific catch, chaining |
| Type issue | Strict types, validation |
| SQL injection | Prepared statements |
| Infinite loop | Iteration limit, cycle detection |
Step 4: Generate Fix
Apply minimal change principles:
- Fix ONLY what's broken
- Preserve API contract
- Maintain existing behavior
- Add validation at appropriate level
Step 5: Quality Checks
Use existing skills to verify fix quality:
acc:detect-code-smells— no new smells introducedacc:detect-memory-issues— no memory leaksacc:analyze-solid-violations— SOLID respectedacc:check-encapsulation— encapsulation intactacc:check-side-effects— side effects preservedacc:check-immutability— immutability maintained
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.
- 6d ago First seen · 165 lines · 31 tokens per session scan A e63db0606c43
bug-fixer is an agent published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 20d ago), licensed MIT. It adds 31 tokens to every session and 1,059 once invoked, about $0.0002 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-30.
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.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.