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 kunalsuri/ai-fication-kit --skill fix-buggit clone --depth 1 https://github.com/kunalsuri/ai-fication-kitWrote 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/kunalsuri/ai-fication-kit/fix-bug)<a href="https://agentmods.dev/skills/kunalsuri/ai-fication-kit/fix-bug"><img src="https://agentmods.dev/badge/skills/kunalsuri/ai-fication-kit/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/kunalsuri/ai-fication-kit/fix-bug"><img src="https://agentmods.dev/badge/skills/kunalsuri/ai-fication-kit/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.00048 | $0.00551 |
| Opus 5.5 | $0.00019 | $0.00220 |
| Sonnet 5.5 | $0.00010 | $0.00110 |
| Haiku 4.5 | $0.00005 | $0.00055 |
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 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.
What it actually says
Fix a bug
The contract: no fix before a reproduction, no reproduction without a failing test, no "fixed" without the regression test green, no closing without the ledger row and the gotcha recorded.
1. Reproduce
Draft ai/lab/specs/BUGFIX_<name>.md from BUGFIX_TEMPLATE.md: symptom
(observed vs expected), exact reproduction steps. Get the user's OK.
2. Prove
Turn the reproduction into a regression test and watch it fail. A bug you cannot make a test fail for is a bug you do not understand yet. The test is permanent — it outlives the fix.
3. Locate
ai/guide/MODULE_MAP.md→ which modules; note Stability of every suspect.ai/guide/FEATURE_MAP.mdgotchas +ai/lab/WORKLOG.md→ was this area recently touched, or is the "bug" deliberate behavior a past ADR explains?- Keep broad reading read-only and cheap (directory listings, manifests, search hits over whole-file reads) to protect context.
4. Gate
Root cause in a file with Stability frozen or ? ⇒ stop and ask the human.
Record their approval in the bugfix doc before proceeding.
5. Diagnose, then fix
Name the root cause in the bugfix doc — the defect, not the symptom. Then make the smallest diff that turns the regression test green. Match the license headers of neighboring files. No drive-by refactors, no layout changes, no dependency additions while "in there".
6. Verify
Run the regression test (now green), then the suites covering the touched area. Report command run · exit status · failures verbatim. Red or unrun ⇒ not fixed.
7. Review & record
Request /review-change on the diff (fresh context — not this session).
Append a bugfix row to ai/lab/WORKLOG.md linking the bugfix doc and review;
add the gotcha line to FEATURE_MAP so the next agent knows the trap. All
[inferred] — tell the user which tags await their [verified] flip.
What ships with it
1 file 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 · 48 lines · 48 tokens per session scan A fbc1c56967aa
fix-bug is a skill published in the GitHub repository kunalsuri/ai-fication-kit (3 stars, last pushed 10d ago), licensed Apache-2.0. It adds 48 tokens to every session and 551 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
superpowers
Runs 14 numbered engineering protocols in one pack — brainstorm, spec, plan, scaffold, TDD red-green-refactor, systematic debugging, refactoring, code review, performance, security, docs, git hygiene, release checklist, postmortem. Use when the user says "build this feature properly", "debug this systematically"…
nazgul:heartbeat
Run one Nazgul automation-heartbeat tick — triages the work inbox and auto-starts the next objective if idle. Opt-in and default-off; fired by an optional Claude Code native scheduled agent (routine) or run by hand. Use when asked to "run a heartbeat tick", "check the inbox", or to test/debug the heartbeat.
doubt-driven-development
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when you want every assumption cross-examined before proceeding, when stress-testing a plan for hidden failure modes, when correctness matters more than speed, when working in unfamiliar code, when stakes are high…
agent-qa-debug-fix
Debug, patch, and verify failed Agent QA runs from MCP evidence, artifacts, logs, and local code without hiding product or infrastructure defects.
mantis-plan
Formulates a targeted defensive security reviewing plan based on the active threat model and historical learnings. Use when starting a security review campaign to map the codebase boundaries and generate a roadmap (workspace/plan.json). Don't use for executing code reviews, writing test scripts, or patching code.
code-review
Reviews code for bugs, security issues, and best practices.