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 agentmods add skills/escapeboy/ai-prompts/fix-bugnpx skills add escapeboy/ai-prompts --skill fix-buggit clone --depth 1 https://github.com/escapeboy/ai-promptsWrote 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/escapeboy/ai-prompts/fix-bug)<a href="https://agentmods.dev/skills/escapeboy/ai-prompts/fix-bug"><img src="https://agentmods.dev/badge/skills/escapeboy/ai-prompts/fix-bug.svg" alt="Measured on agentmods" 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 | $0.00030 | $0.00595 |
| Opus 5 | $0.00015 | $0.00298 |
| Sonnet 5 | $0.00006 | $0.00119 |
| Haiku 4.5 | $0.00003 | $0.00060 |
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 5d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
fix-bug
Three-phase bug fix that finds ALL occurrences, fixes atomically, and validates with a regression test.
Phase 1 — Comprehensive Investigation
Before touching any code:
- Reproduce the issue and capture the exact error message / stack trace
- Identify the primary symbol involved (function name, route, variable, class, column)
- Grep the entire codebase for every reference to that symbol:
- Controllers, services, models
- View templates (Blade / JSX / ERB / Twig — server-rendered views are the most-missed spot)
- Tests (feature + unit)
- Route definitions (all route files, not just the obvious one)
- Config files
- JS/CSS files if relevant
- Document: full list of files that reference the broken symbol
- Check for the same bug pattern in similar locations (e.g. if one route is broken, check all routes of the same type)
Do not proceed until you have the complete reference map.
Phase 2 — Fix with Full Coverage
Apply changes atomically across every file found in Phase 1:
- For renamed variables/properties: update the definition + every view, controller, test, and config
- For broken routes: check all route files, all route-helper calls, all redirects and links
- For removed/changed model attributes: update mass-assignment lists (
$fillableor equivalent), factories, seeders, and all tests that reference those attributes - For middleware changes: check route groups, kernel/middleware registration, and all test middleware overrides
After applying all changes, grep again to confirm zero remaining old references.
Phase 3 — Validate
- Run the full test suite (
php artisan test --parallel,npm test,pytest— project equivalent) - If tests fail:
- Determine: is the test wrong, or is the fix incomplete?
- Never change test assertions to make them pass trivially
- Fix the underlying issue
- Write a regression test that:
- Reproduces the original bug (assert it was broken)
- Confirms the fix works
- Lives in the appropriate test directory
- Final grep: confirm zero references to the old broken pattern
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.
- 5d ago First seen · 63 lines · 30 tokens per session scan A 3e48ed70a8a2
fix-bug is a skill published in the GitHub repository escapeboy/ai-prompts (91 stars, last pushed 10d ago), licensed MIT. It adds 30 tokens to every session and 595 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…