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/leekjay/claude-skills-plugin/bug-fixnpx skills add LeekJay/claude-skills-plugin --skill bug-fixgit clone --depth 1 https://github.com/LeekJay/claude-skills-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/leekjay/claude-skills-plugin/bug-fix)<a href="https://agentmods.dev/skills/leekjay/claude-skills-plugin/bug-fix"><img src="https://agentmods.dev/badge/skills/leekjay/claude-skills-plugin/bug-fix.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.1 | $0.00045 | $0.04531 |
| Opus 5 | $0.00023 | $0.02266 |
| Sonnet 5 | $0.00009 | $0.00906 |
| Haiku 4.5 | $0.00005 | $0.00453 |
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 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 — 763 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Fix Skill
Overview
This skill provides intelligent bug fixing capabilities through a hybrid architecture:
- Skill mode: Direct handling in main conversation for simple, isolated bugs
- Sub-agent mode: Delegate complex, multi-file bugs to isolated executor context
When to Use This Skill
✅ Use This Skill For:
Bug Identification & Analysis:
- Diagnosing runtime errors and exceptions
- Analyzing stack traces and error messages
- Identifying root causes of unexpected behavior
- Tracing bugs through call chains
Simple Bug Fixes:
- Single-file bug fixes
- Logic errors in specific functions
- Off-by-one errors and boundary conditions
- Type errors and null/undefined issues
- Simple state management bugs
Complex Bug Fixes:
- Bugs spanning multiple files
- Race conditions and concurrency issues
- Memory leaks and performance bugs
- Integration bugs across modules
- Data consistency issues
Regression Fixes:
- Bugs introduced by recent changes
- Breaking test cases
- API contract violations
- Behavior changes affecting downstream code
❌ Don't Use For:
- Feature requests (not bugs)
- Code refactoring (unless fixing a bug)
- Performance optimization (unless it's a performance bug)
- Code style improvements
- Adding new functionality
Decision Framework
Default behavior: For bug fixing tasks, prefer Sub-Agent mode unless the task is clearly simple.
🔴 Mandatory Sub-Agent Triggers (ANY ONE triggers delegation)
- Multi-file scope: Bug description mentions 2+ files or modules
- Unknown root cause: Requires investigation ("sometimes...", "occasionally...", "intermittent...")
- Complex keywords: Description contains race condition, memory leak, data inconsistency, state sync, cache issues, deadlock
- Cross-layer issues: Involves frontend+backend, multiple services, database+application layer
- Debugging required: Needs logging, breakpoints, execution flow tracing
- Regression/recurring: Bug existed before, was fixed but reappeared, or has history
- Test-related: Needs test writing for verification, involves test framework issues
- Unclear reproduction: User cannot reliably reproduce the bug
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 · 763 lines · 45 tokens per session scan A 021efd9fcc8e
bug-fix is a skill published in the GitHub repository LeekJay/claude-skills-plugin (4 stars, last pushed 8mo ago), licensed MIT. It adds 45 tokens to every session and 4,531 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-31.
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…