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 mthines/agent-skills --skill fix-buggit clone --depth 1 https://github.com/mthines/agent-skillsWrote 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/mthines/agent-skills/fix-bug)<a href="https://agentmods.dev/skills/mthines/agent-skills/fix-bug"><img src="https://agentmods.dev/badge/skills/mthines/agent-skills/fix-bug/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/mthines/agent-skills/fix-bug"><img src="https://agentmods.dev/badge/skills/mthines/agent-skills/fix-bug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 485 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Excessive Agency · line 724 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00095 | $0.05373 |
| Opus 5.5 | $0.00038 | $0.02149 |
| Sonnet 5.5 | $0.00019 | $0.01075 |
| Haiku 4.5 | $0.00010 | $0.00537 |
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.
How it starts
The opening of the file, as written. The whole thing — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix Bug
Take a bug in any form and either ship a verified draft PR or hand back an evidence-backed proposal. This skill runs evidence intake, root-cause analysis, and verification itself; gating, repro authoring, planning, and implementation run in the skills and agents each phase names.
Contents
Phases: 0 Intake → 0.5 Triage → 1 Evidence → 2 Repro lock → 3 Analysis → 4 Confidence → 5 Decision → 6 Handoff → 7 Verify → 8 Telemetry; then Lesson writes and Output Format.
The bug-notes ledger at .agent/<branch>/bug-notes.md is read on entry and appended on exit by every phase — rules/bug-notes-ledger.md.
Read rules/prerequisites.md when a dependency (agent, skill, CLI, MCP) is missing or may be optional.
Read references/design-rationale.md or references/research-sources.md when you need the why behind a gate or threshold.
Phase 0 — Intake & Classification
Step 0a — Detect mode flags
| Flag | Action |
|---|---|
--analyse-only (or --analyze-only) |
Set ANALYSE_ONLY=true. Continue to step 0b. |
--force-holistic |
Set FORCE_HOLISTIC=true. Continue to step 0b. Phase 0.5 will skip its decision and pick complex. |
--verify-deploy <PR> |
Set VERIFY_DEPLOY_MODE=true and VERIFY_DEPLOY_PR=<PR>. Skip steps 0b–0c; follow rules/verify-deploy.md. |
If two or more flags are present, fail with
--analyse-only, --force-holistic, and --verify-deploy are mutually exclusive.
Strip the matched flag (and its argument, for --verify-deploy) from $ARGUMENTS.
Print one mode line only if a flag matched:
What ships with it
20 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.
- references/design-rationale.md 7.6 KB
- references/research-sources.md 9.4 KB
- rules/autonomous-handoff.md 12 KB
- rules/bug-notes-ledger.md 5.5 KB
- rules/complexity-triage.md 10 KB
- rules/diagnostic-surface.md 27 KB
- rules/evidence-resolution.md 8.8 KB
- rules/fast-lane-plan-contract.md 17 KB
- rules/gate-errors.md 3.8 KB
- rules/independent-verification.md 6.7 KB
- rules/output-format.md 1.4 KB
- rules/preflight.md 4.7 KB
- rules/prerequisites.md 2.3 KB
- rules/reproduction.md 17 KB
- rules/root-cause-analysis.md 4.6 KB
- rules/self-improvement-loop.md 14 KB
- rules/telemetry-verification.md 11 KB
- rules/verify-deploy.md 2.1 KB
- templates/bug-fix-pack.md 2.4 KB
- templates/bug-notes.md 3.5 KB
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.
- 4d ago Changed 695fb08db1c8
- 6d ago Changed · -585 lines · -151 tokens per session 61fc4fec3992
- 27d ago Changed · -1 lines dd4e9841e4f1
- 1mo ago Changed · -3 lines · -97 tokens per session b1a5e964cec4
- 1mo ago Changed bbb77b840bb2
- 1mo ago Changed · +8 lines 3a81cbb62e49
- 1mo ago First seen · 872 lines · 343 tokens per session scan A ad1ec0fdf0e6
fix-bug is a skill published in the GitHub repository mthines/agent-skills (20 stars, last pushed yesterday), licensed MIT. It adds 95 tokens to every session and 5,373 once invoked, about $0.0004 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-03.
Other skills, from other repositories
health
Audits agent config, instruction drift, hooks or MCP, and AI maintainability. Use when Claude, Codex, or Pi setup looks wrong. Not for application bugs or PR review.
hunt
Finds root cause before any fix. Use when something errors, crashes, regresses, or used to work. Not for code review or new features.
ego-lite-simplify
Find and implement evidence-backed simplifications in the ego-lite repository. Use when reviewing the codebase for dead code, duplicated state or APIs, speculative abstractions, unnecessary compatibility layers, hand-written infrastructure, excessive tests or documentation, or when the user asks to reduce code size or…
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.
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)…
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…