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 skills add kardebadas/claude-plugin --skill bug-fixgit clone --depth 1 https://github.com/kardebadas/claude-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/skills/kardebadas/claude-plugin/bug-fix)<a href="https://agentmods.dev/skills/kardebadas/claude-plugin/bug-fix"><img src="https://agentmods.dev/badge/skills/kardebadas/claude-plugin/bug-fix/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/skills/kardebadas/claude-plugin/bug-fix"><img src="https://agentmods.dev/badge/skills/kardebadas/claude-plugin/bug-fix.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.00074 | $0.02203 |
| Opus 5.5 | $0.00030 | $0.00881 |
| Sonnet 5.5 | $0.00015 | $0.00441 |
| Haiku 4.5 | $0.00007 | $0.00220 |
Grade A, and why
bug-fix 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Fix
Overview
Carries a bug from report to validated fix by chaining specialists: investigate → decide → plan → implement. You are the conductor. Investigation and implementation each go to a specialist wherever one is available, and this skill owns the seams and the evidence bar between them.
Core principle: no fix is planned until the root cause is proven with
file:line evidence, and no plan is written until the open questions are
answered. Do not guess. A plausible fix for an unproven cause is worse than
no fix: it consumes the report, closes the ticket, and leaves the bug live.
When NOT to use
- Building new behaviour — that is
superb:craftthensuperb:pipeline. - A change whose cause is already proven — skip to the fix; the investigation exists to establish a cause, not to ceremonially confirm one.
- A whole feature's worth of bugs — that is a phase of
superb:pipeline, which has the fix loop, the findings ledger and the convergence rule. - You only want to know what is wrong — that is
superb:bug-investigate, which runs this skill's Step 1 and stops. Reach for it when the decision to fix has not been made, or when naming the cause is the whole deliverable.
Step 0 — Assemble the report
The investigator needs five things. The invocation argument usually supplies one or two:
| Field | Example |
|---|---|
| Symptom | "uploads over ~5MB fail silently" |
| Reproduction | the steps, or unknown |
| Error text | stack trace, log line, or none surfaced |
| Affected surface | endpoint, screen, command, job |
| Last known good | a date, a release, a commit, or never worked |
Ask the user for whatever is missing before dispatching — one batched
question, not five. unknown is a fine answer and belongs in the brief; a
silently empty field is not, because the investigator will fill it with a guess.
If the symptom itself is unclear, stop: there is nothing to investigate yet.
Step 1 — Investigate
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 180 lines · 74 tokens per session scan A 9f54b80c6c49
bug-fix is a skill published in the GitHub repository kardebadas/claude-plugin (3 stars, last pushed 22d ago), licensed Apache-2.0. It adds 74 tokens to every session and 2,203 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-09-05.
Other skills, from other repositories
diagnose-project
Diagnose .NET SDK, restore, build, test, package, target framework, F# compile-order, C# analyzer, and project-reference failures with concrete next checks.
xcode-build-run-workflow
Guide build, run, preview-adjacent, workspace-inspection, diagnostics, toolchain, and guarded mutation work in existing Xcode-managed projects and workspaces. Use when Xcode-aware execution is needed and the task is primarily about build, run, or project-integrity work rather than testing.
safari-mcp-workflow
Inspect a scoped live site in Safari through Safari Technology Preview's local MCP server. Use for Safari-specific DOM, console, network, screenshot, accessibility, performance, interaction, responsive, or print-media evidence.
xcode-debugger-mcp-workflow
Diagnose a running Apple app through Xcode’s active LLDB debugging session and assess the experimental Xcode 27 lldb-mcp executable. Use when setting breakpoints, inspecting frames or variables, issuing LLDB commands, or distinguishing a usable Xcode debugger session from an unavailable standalone debugger MCP server.
xcode-device-hub-workflow
Manage and validate simulated and physical Apple devices through Xcode Device Hub. Use when selecting or inspecting run destinations, interacting with an app, changing simulated-device environment settings, capturing screenshots or videos, pairing a device, or collecting diagnostics.
ios-runtime-forensics-workflow
Capture and interpret reproducible iOS Simulator performance and memory evidence. Use when an iOS issue needs ETTrace/symbolication, a memgraph, leak ownership traces, or before/after runtime proof rather than a code-only guess.