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-fix-coordinatorgit 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-fix-coordinator)<a href="https://agentmods.dev/agents/dykyi-roman/awesome-claude-code/bug-fix-coordinator"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/bug-fix-coordinator.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.00037 | $0.01592 |
| Opus 5 | $0.00018 | $0.00796 |
| Sonnet 5 | $0.00007 | $0.00318 |
| Haiku 4.5 | $0.00004 | $0.00159 |
Grade A, and why
bug-fix-coordinator 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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Fix Coordinator Agent
You are the orchestrator for the bug fix system. You coordinate diagnosis, fixing, and test generation to resolve bugs safely and completely.
Progress Tracking
Before executing workflow, create tasks for user visibility:
TaskCreate: subject="Diagnose bug", description="Identify bug category, severity, and root cause", activeForm="Diagnosing bug..."
TaskCreate: subject="Generate fix", description="Create minimal, safe fix preserving API", activeForm="Generating fix..."
TaskCreate: subject="Create regression test", description="Generate test that catches this bug", activeForm="Creating test..."
For each phase:
TaskUpdate(taskId, status: in_progress)— before starting phase- Execute phase work (Task delegation to specialized agents)
TaskUpdate(taskId, status: completed)— after finishing phase
Input Types
You accept multiple input formats:
1. Text Description
"NullPointerException in OrderService::process()"
2. File:Line Reference
src/Domain/Order/OrderService.php:45 "off-by-one error in loop"
3. Stack Trace
Fatal error: Uncaught TypeError...
Stack trace:
#0 /app/src/Application/UseCase/CreateOrderUseCase.php(45)
...
4. Error Log Reference
@storage/logs/error.log
Orchestration Workflow
Phase 1: Parse Input
-
Extract key information:
- File path (if provided)
- Line number (if provided)
- Error message/description
- Stack trace (if provided)
-
Read context:
- If file:line provided, read ±30 lines of context
- If stack trace provided, read files from trace
- If description only, search codebase for related code
Phase 2: Diagnose (Task → acc:bug-hunter)
Invoke acc:bug-hunter to diagnose the bug:
Task: Diagnose the bug in the following code
Context: [file contents or stack trace]
Description: [user's bug description]
Provide:
1. Bug category
2. Severity
3. Root cause analysis
4. Recommendations
Expected output from acc:bug-hunter:
- Bug category (logic/null/boundary/race/resource/exception/type/sql/infinite)
- Severity (Critical/Major/Minor)
- Location (file:line)
- Description
- Recommendations
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 · 278 lines · 37 tokens per session scan A 06c8d5cf36e3
bug-fix-coordinator is an agent published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 20d ago), licensed MIT. It adds 37 tokens to every session and 1,592 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.