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 Aquifer-sea/pattern8 --skill bug_fixgit clone --depth 1 https://github.com/Aquifer-sea/pattern8Wrote 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/aquifer-sea/pattern8/bug_fix)<a href="https://agentmods.dev/skills/aquifer-sea/pattern8/bug_fix"><img src="https://agentmods.dev/badge/skills/aquifer-sea/pattern8/bug_fix/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/aquifer-sea/pattern8/bug_fix"><img src="https://agentmods.dev/badge/skills/aquifer-sea/pattern8/bug_fix.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.00025 | $0.00346 |
| Opus 5.5 | $0.00010 | $0.00138 |
| Sonnet 5.5 | $0.00005 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00035 |
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 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
Bug Fix
Constrains the Agent to follow the "locate → root cause analysis → fix → regression verification" structured process.
Step 1: Inversion (Requirements Alignment)
Before fixing a bug, you must check every item in assets/checklist.yaml.
Step 2: Generator (Generate Fix Report from Template)
Your output must strictly follow the format defined in assets/template.yaml.
Must include: root cause analysis, fix plan, fix code (diff format), impact analysis, regression checklist.
Vague suggestions like "try changing this" are not allowed.
Step 3: Tool Wrapper (Security Fence)
If you need to execute commands to reproduce or verify a bug, check references/security.yaml first.
Do not execute any high-risk commands that could damage existing code or environment.
Step 4: Reviewer (Self-Audit Loop)
After fixing, audit your fix against references/guidelines.yaml.
Key checks: does the fix address the root cause? Does it introduce new bugs? Is the diff minimal?
Roll back and regenerate if non-compliant, up to 3 retries.
What ships with it
4 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.
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 · 45 lines · 25 tokens per session scan A 140b0b5b42b5
bug_fix is a skill published in the GitHub repository Aquifer-sea/pattern8 (44 stars, last pushed 6mo ago), licensed MIT. It adds 25 tokens to every session and 346 once invoked, about $0.0001 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-30.
Other skills, from other repositories
cause-and-effect
Systematic Fishbone analysis exploring problem causes across six categories.
root-cause-tracing
Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior.
why
Iterative Five Whys root cause analysis drilling from symptoms to fundamentals.
mastra-api
Interact with Mastra development server API for debugging agents, viewing conversation threads, listing/inspecting tools and workflows, accessing observability data, and managing Mastra resources. Use when working with Mastra agents and need to inspect runtime state, debug agent errors, view thread history, see…
cradle-observability-debugger
Debug Cradle local observability data by querying SQLite events/incidents/timeline, runtime snapshots, metrics, and server logs.
debug
Structured debugging assistant. Use /debug to get a guided diagnosis of any bug — Claude will ask the right questions and then pinpoint the root cause.