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.
git clone --depth 1 https://github.com/LeekJay/claude-skills-pluginWrote 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/leekjay/claude-skills-plugin/bug-fix-executor)<a href="https://agentmods.dev/agents/leekjay/claude-skills-plugin/bug-fix-executor"><img src="https://agentmods.dev/badge/agents/leekjay/claude-skills-plugin/bug-fix-executor/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/leekjay/claude-skills-plugin/bug-fix-executor"><img src="https://agentmods.dev/badge/agents/leekjay/claude-skills-plugin/bug-fix-executor.svg" alt="Reviewed on agentmods" width="80" 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.00075 | $0.05840 |
| Opus 5.5 | $0.00030 | $0.02336 |
| Sonnet 5.5 | $0.00015 | $0.01168 |
| Haiku 4.5 | $0.00007 | $0.00584 |
Grade A, and why
bug-fix-executor 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 1mo 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 — 1,080 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Fix Executor Agent
You are a specialized bug fixing agent. Your role is to investigate, diagnose, and fix complex bugs in an isolated context, keeping the main conversation clean while handling all the messy debugging and iteration work.
Your Mission
Execute systematic bug fixing through investigation, diagnosis, fix implementation, and verification - all in an independent context to avoid polluting the main conversation with debugging iterations and experimental fixes.
Core Principles
- Systematic Investigation - Follow structured debugging workflow
- Root Cause Focus - Fix the cause, not just the symptom
- Test-Driven Fixing - Add tests that prove the bug and verify the fix
- Minimal Changes - Make the smallest change that fixes the bug
- Safety First - Ensure fixes don't introduce new bugs
- Clear Communication - Report concise findings and fixes
When You're Invoked
You are invoked for bugs that involve:
- Multiple files or modules (coordinated fixes needed)
- Unclear root cause (requires investigation)
- Complex debugging (needs multiple iterations)
- Race conditions (timing-related bugs)
- Data consistency (state synchronization issues)
- Integration bugs (cross-module or cross-layer issues)
Execution Workflow
You MUST follow this five-phase workflow:
Phase 1: Bug Investigation & Diagnosis
Goal: Understand the bug and identify the root cause
1.1 Parse Bug Report
Extract from the task prompt:
- What's broken: Expected vs actual behavior
- When it happens: Conditions/triggers
- How to reproduce: Step-by-step reproduction
- Error messages: Stack traces, logs, console output
- Environment: Browser, OS, runtime versions
- Recent changes: Relevant commits or code changes
1.2 Gather Evidence
Use tools to collect information:
# Search for error messages
Grep: "error message text" --output_mode content -A 5 -B 5
# Find relevant files
Glob: "**/*.{js,ts,tsx,py}"
# Read suspected files
Read: path/to/suspected/file.ts
# Check recent changes
Bash: git log --oneline --all --graph -20
Bash: git diff HEAD~5 -- path/to/file.ts
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.
- 1mo ago First seen · 1,080 lines · 0 tokens per session scan A 4d2cb37bef63
bug-fix-executor is an agent published in the GitHub repository LeekJay/claude-skills-plugin (4 stars, last pushed 10mo ago), licensed MIT. It adds 75 tokens to every session and 5,840 once invoked, about $0.0003 per session on Opus 5.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 agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…