agentmods.dev

bugfix

Instructions for diagnosing and fixing bugs or regressions, meaning behavior that is broken or has become incorrect after a change. The workflow includes reproducing the problem, finding its cause, applying a focused fix, and verifying it.

In plain words
What is it for?
Reproducing failures, reading the responsible code, adding regression tests, running the project's checks, updating the changelog when needed, and preparing pull requests in the project's required format.
Why use it?
It keeps debugging tied to the original failure and reduces the risk of fixing only the symptom or introducing another problem.

Skill for Claude CodeCodexCursor

4 2d ago A scan 38 tokens original Apache-2.0
View the source file LAA-Software-Engineering/terfyn
Install

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.

agentmods
npx agentmods add skills/laa-software-engineering/terfyn/bugfix
Any agent
npx skills add LAA-Software-Engineering/terfyn --skill bugfix
Clone the repo
git clone --depth 1 https://github.com/LAA-Software-Engineering/terfyn

Made for: Claude Code, Codex, Cursor.

Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 322 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00038 $0.00322
Opus 5 $0.00019 $0.00161
Sonnet 5 $0.00008 $0.00064
Haiku 4.5 $0.00004 $0.00032

Measured 2d ago against content hash b169f74f4a6c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

.cursor/skills/bugfix/SKILL.md · 23 lines

What it actually says

Bugfix

Workflow

  1. Reproduce — Capture the failing command, test, or CLI path. Prefer a failing test over manual-only repro.
  2. Root cause — Read the failing code path; identify the real cause before patching symptoms.
  3. Minimal fix — Change only what is required. Match nearby error-handling and style.
  4. 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_
  5. Verify — Run make ci. Confirm the original failure is gone.
  6. Changelog — If user-visible, note under Unreleased in CHANGELOG.md.
  7. Pull request — When opening a PR, read .github/PULL_REQUEST_TEMPLATE.md and use that exact structure for the body (HEREDOC with gh 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.md and existing CLI exit handling before changing behavior.
  • Prefer fixing at the package boundary that owns the bug (internal/cli, internal/engine, internal/policy, etc.).
Changes

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.

  1. 2d ago First seen · 23 lines · 38 tokens per session scan A b169f74f4a6c

Subscribe to this mod's changes

bugfix is a skill published in the GitHub repository LAA-Software-Engineering/terfyn (4 stars, last pushed 2d ago), licensed Apache-2.0. It adds 38 tokens to every session and 322 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.

DebuggingGit and workflowTestingagentsai-agentsclideclarativegitopsgolang
Related

Other skills, from other repositories

qa-find-bugs

Drive the live product at https://dashboard.bex.co as a signed-in QA user (QAEMAIL / QAPASSWORD from .env), hunt real bugs across the hosting features, research each fix down to file:line, file the non-duplicate findings to the w6 board through /pm, and /ship the scheduled milestone. Use when the user asks to QA the…

bex-co/bex · 96 tokens

pm

Inspect and maintain the repository's .pm workstreams, inbox notes, milestones, and tasks. Use when the user asks for PM board status or requests a supported board mutation such as creating, promoting, adding, or completing work.

bex-co/bex · 48 tokens

stripe-projects

Use when the user wants to provision infrastructure or third-party services using Stripe Projects. Triggers: "I need a database", "set up auth", "add caching", "give me a Postgres", "provision Redis", "I need hosting", "add a vector DB", "get me an API key for X", "get credentials for X", "sign up for a service", "set…

bex-co/bex · 213 tokens

deploy-app-from-local

Deploy a local checkout to a production Hetzner App using the manual image-import runbook. Use when the user asks to ship local working-tree code to a live bex App rather than deploy from remote Git. Arguments are the local repo path and app name.

bex-co/bex · 58 tokens

ship

Safely bring main up to date, commit intended pending changes, and push to origin/main. Use when the user explicitly asks to ship the current main branch or invokes the repository's ship workflow.

bex-co/bex · 41 tokens

mock-cluster

Stand up or scale the local CAPD mock cluster and deploy the bex operator into it. Use when the user asks to create, inspect, or resize the repository's local development cluster. Optional argument: scale N.

bex-co/bex · 48 tokens