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/Amey-Thakur/AI-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/commands/amey-thakur/ai-skills/agent-fix-bug)<a href="https://agentmods.dev/commands/amey-thakur/ai-skills/agent-fix-bug"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/agent-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/commands/amey-thakur/ai-skills/agent-fix-bug"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/agent-fix-bug.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.00026 | $0.00394 |
| Opus 5 | $0.00013 | $0.00197 |
| Sonnet 5 | $0.00005 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
agent-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 12d 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.
What it actually says
You were invoked as a slash command. The user's input:
$ARGUMENTS
Use that input to fill this prompt's variables (take the main content, topic, or task from it; ask only if a required value is missing and not supplied), then follow the prompt exactly.
You are a coding agent. Find and fix the root cause of this bug. Do not patch the symptom.
BUG: {bug}
CONTEXT: {context}
Process, in order:
- Reproduce it first. Confirm you can trigger the bug and see the wrong behavior. If you cannot reproduce it, say so and ask for what you need: do not guess at a fix for a bug you have not seen.
- Find the root cause. Trace the actual execution path to where the behavior goes wrong. State the root cause in one sentence before fixing. Do not fix the first plausible-looking line; fix the cause.
- Fix it minimally. Change the least code that correctly addresses the root cause. Do not rewrite surrounding code or add unrelated changes.
- Prove it is fixed: reproduce the original scenario and show it now behaves correctly. Run the existing tests to confirm you broke nothing. Add a regression test that would have caught this bug, if the project has tests.
- Check for the same bug elsewhere: if this pattern could exist in other places, note them.
Report: the root cause, the fix and why it is correct, how you verified it, and the regression test.
Rules: be honest if the root cause is uncertain or the fix is a mitigation rather than a true fix. Do not claim it is fixed without demonstrating it.
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.
- 12d ago First seen · 43 lines · 26 tokens per session scan A 50072a55719f
agent-fix-bug is a command published in the GitHub repository Amey-Thakur/AI-SKILLS (7 stars, last pushed 6d ago), licensed MIT. It adds 26 tokens to every session and 394 once invoked, about $0.0001 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-31.
Other commands, from other repositories
fit-check
Audit a design or subsystem for primitive/problem fit (the wrong-primitive trap). Runs the architecture-fit-check skill.
perf-audit
Profile a performance complaint and fix the biggest contributor with Instruments and MetricKit.
swift6-fix
Diagnose and fix Swift 6 strict concurrency, Sendable, or MainActor isolation errors.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.