fix-bug

fix-bug is a skill for Claude Code from mthines/agent-skills. It costs 343 tokens per session (12,526 once invoked), scanned A, original, MIT.

A bug-fixing workflow that starts from evidence such as telemetry, a stack trace, an error message, a code location, a recording, or a ticket.

In plain words
What is it for?
It is for diagnosing and fixing software bugs, then choosing suitable tests and an implementation approach based on the problem's complexity.
Why use it?
It gives different kinds of bug reports a consistent investigation path and can return either a verified draft fix or an evidence-based proposal.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: mentions subagents.

Part of the mthines-agent-skills plugin — 55 skills, 4 agents shipped together

Good fit It is for diagnosing and fixing software bugs, then choosing suitable tests and an implementation approach based on the problem's complexity.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mthines/agent-skills/fix-bug
Install

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.

Any agent
npx skills add mthines/agent-skills --skill fix-bug
Clone the repo
git clone --depth 1 https://github.com/mthines/agent-skills

Made for: Claude Code.

Or install mthines-agent-skills, the plugin that ships this one along with the rest of its 55 skills, 4 agents.

Wrote 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.

agentmods badge for fix-bug

README.md
[![agentmods](https://agentmods.dev/badge/skills/mthines/agent-skills/fix-bug.svg)](https://agentmods.dev/skills/mthines/agent-skills/fix-bug)
Your own site
<a href="https://agentmods.dev/skills/mthines/agent-skills/fix-bug"><img src="https://agentmods.dev/badge/skills/mthines/agent-skills/fix-bug.svg" alt="Measured on agentmods" height="20"></a>
Per session 343 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 12,526 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00343 $0.12526
Opus 5 $0.00171 $0.06263
Sonnet 5 $0.00069 $0.02505
Haiku 4.5 $0.00034 $0.01253

Measured 4d ago against content hash ad1ec0fdf0e6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

fix-bug 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 4d 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.

skills/workflow/fix-bug/SKILL.md · 872 lines

How it starts

The opening of the file, as written. The whole thing — 872 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Fix Bug

Take a bug — described in any form the user has at hand — and either ship a verified draft PR with the fix or hand back a clear, evidence-backed proposal. This skill is a thin orchestrator: heavy reasoning lives in holistic-analysis (dispatched isolated via the rca-investigator agent on the complex lane), gating in confidence, test authoring in /tdd / /e2e-testing / /e2e-testing-mobile, plan authoring in aw-planner (standard-lane) or aw-create-plan (fast-lane), implementation in aw-executor, and independent grading in bug-fix-verifier. This skill owns input classification, complexity triage, evidence assembly, the user-facing decision at the confidence boundary, lane selection, and a durable bug-notes ledger that survives compaction.

Source of truth. This SKILL.md is a thin index. Detailed procedures live in rules/*.md, literal artefacts in templates/*.md, and external references in references/*.md. Load only what the current phase asks for.

Architecture

Phase 0:   Intake                     → classify input + infer bugClass + detect mode flags
Phase 0.5: Complexity Triage          → simple | complex (signals + decision rule)
Phase 1:   Evidence Resolution        → per-input resolution + pre-flight sweep (may upgrade triage)
Phase 2:   Source Mapping + Repro Lock → Evidence Record + failing repro (via /tdd or /e2e-testing*)
Phase 3:   Analysis                   → Task(rca-investigator) — isolated holistic-analysis + confidence [complex]
                                      OR lightweight in-skill analysis [simple]
Phase 4:   Confidence Gate            → /confidence analysis
Phase 5:   Branch Decision            → >= 92 % auto-implement (no human confirmation);
                                       80–91 % stop with raise-the-score guidance,
                                       force-proceed offered (routes standard-lane);
                                       70–79 % stop, force-proceed flagged NOT recommended;
                                       < 70 % stop, no force-proceed.
                                       --analyse-only always stops here.
Phase 6:   Autonomous Handoff (lane-split)
             ├── Fast-lane (simple + >= 92 %):
             │     /fix-bug → Skill("aw-create-plan", ...) → aw-executor
             │     Round-3 CEGIS failure → fall back to standard-lane via aw-planner.
             └── Standard-lane (complex / downgrade / force-proceed):
                   aw-planner → aw-executor (canonical path).
Phase 7:   Independent Verification   → bug-fix-verifier (fresh context) decides PR undraft
                                       Identical for both lanes.
Phase 8:   Telemetry Verification     → poll originating Dash0 query post-deploy (telemetry inputs)

Read the full file on GitHub · 872 lines

Changes

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.

  1. 4d ago First seen · 872 lines · 343 tokens per session scan A ad1ec0fdf0e6

Subscribe to this mod's changes

fix-bug is a skill published in the GitHub repository mthines/agent-skills (12 stars, last pushed yesterday), licensed MIT. It adds 343 tokens to every session and 12,526 once invoked, about $0.0017 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-09-03.

Related

Other skills, from other repositories

testing-dags

Complex DAG testing workflows with debugging and fixing cycles. Use for multi-step testing requests like "test this dag and fix it if it fails", "test and debug", "run the pipeline and troubleshoot issues". For simple test requests ("test dag", "run dag"), the airflow entrypoint skill handles it directly. This skill…

astronomer/agents · 77 tokens

experiment-iterative-coder

Iterative code refinement through plan → code → evaluate → refine cycles. Runs lint checks (ruff), tests (pytest), and structured self-evaluation each cycle, then diagnoses failures and refines. Decomposes complex tasks into sequential phases, iterates up to 3 times per phase (10 total). Use when: the main agent…

EvoScientist/EvoSkills · 145 tokens

testing-blocks

Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.

adobe/skills · 61 tokens

qa

Read-only automated QA sweep of a deployed stardust site on AEM Edge Delivery Services — validates routing, content fidelity vs the source capture, template conformance, rendered integrity (geometry, JS errors, broken images), visual regression vs baselines, metadata/SEO/JSON-LD, link integrity, accessibility (axe)…

adobe/skills · 138 tokens

refactoring-patterns

Systematic refactoring techniques, code smell elimination, pattern extraction, and legacy modernization.

cosmicstack-labs/mercury-agent-skills · 21 tokens

run-checks

Run the project's full verification gate: every check the project defines as a pass/fail condition, built from its CI config, check scripts, and configured tools, or from a formatter-linter-test baseline when it declares none. Use when the user asks to "run checks", "run the verification gate", "run lint and tests"…

tobihagemann/turbo · 96 tokens