Borrowing it
Nothing to install: this file belongs to LAA-Software-Engineering/terfyn. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/LAA-Software-Engineering/terfyn/main/.cursor/skills/bugfix/SKILL.mdgit clone --depth 1 https://github.com/LAA-Software-Engineering/terfynWrote 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/laa-software-engineering/terfyn/bugfix)<a href="https://agentmods.dev/skills/laa-software-engineering/terfyn/bugfix"><img src="https://agentmods.dev/badge/skills/laa-software-engineering/terfyn/bugfix/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/laa-software-engineering/terfyn/bugfix"><img src="https://agentmods.dev/badge/skills/laa-software-engineering/terfyn/bugfix.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.00038 | $0.00322 |
| Opus 5.5 | $0.00015 | $0.00129 |
| Sonnet 5.5 | $0.00008 | $0.00064 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
bugfix 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
Bugfix
Workflow
- Reproduce — Capture the failing command, test, or CLI path. Prefer a failing test over manual-only repro.
- Root cause — Read the failing code path; identify the real cause before patching symptoms.
- Minimal fix — Change only what is required. Match nearby error-handling and style.
- Regression test — Add or extend a test that fails without the fix. Update goldens only when intentional:
GO_UPDATE_GOLDEN=1 go test ./internal/cli/... -run TestGolden_ - Verify — Run
make ci. Confirm the original failure is gone. - Changelog — If user-visible, note under Unreleased in
CHANGELOG.md. - Pull request — When opening a PR, read
.github/PULL_REQUEST_TEMPLATE.mdand use that exact structure for the body (HEREDOC withgh pr create). Fill Summary, Test plan, and Checklist. Do not invent a different format.
Tips
- Policy/safety gates and exit codes matter — check
docs/DESIGN_DOC.mdand existing CLI exit handling before changing behavior. - Prefer fixing at the package boundary that owns the bug (
internal/cli,internal/engine,internal/policy, etc.).
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 · 23 lines · 38 tokens per session scan A b169f74f4a6c
bugfix is a skill published in the GitHub repository LAA-Software-Engineering/terfyn (4 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 38 tokens to every session and 322 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
amq-cli
Coordinate coding agents through AMQ. Use for agent messages, inboxes, receipts, sessions, wake delivery, cross-project routing, managed launches, or AMQ diagnostics. Use amq-spec for collaborative design; do not use this for general message queues or single-agent work.
shadow-verify
Dispatch a parallel adversarial verifier wave after any high-stakes sub-agent investigation (code reviews, audits, findings reports, large refactors, gap analyses) — or whenever a sub-agent asserts a claim with high-confidence language, since confidence is a trigger, not a verdict. Use when sub-agent output will drive…
systematic-debugging
Root-causing defects instead of guessing: reproduce, isolate, instrument component boundaries, kill hypotheses, and recognise when to question the design. Use on any bug, flaky test, or unexplained behaviour.
diagnose
Parallel root-cause analysis for bugs and failing tests. Use when a test fails, a bug is reported, or behavior is unexplained — dispatches sub-agents to form and validate hypotheses in isolated worktrees.
hatch3r-incident-response
Handles production incidents with structured triage, mitigation, and post-mortem. Use when responding to production issues, outages, or security incidents.
hatch3r-bug-fix
Step-by-step bug fix workflow. Diagnose root cause, implement minimal fix, write regression test. Use when fixing bugs, working on bug report issues, or when the user mentions a bug.