agentmods.dev

fix-feature-bug

A structured workflow for fixing a bug in a feature or software module. It uses the project's configuration and documentation to classify the problem, make the appropriate correction, and add regression tests.

In plain words
What is it for?
Use it when a feature is broken or produces an error. It helps locate the relevant module, apply the project's correction rules, and test that the bug does not return.
Why use it?
It gives bug fixes a repeatable process and helps distinguish a code mistake from an incorrect specification or other project-level cause.

Skill for Claude CodeCodexCursor

2 1mo ago A scan 17 tokens copy · 92% MIT
View the source file markmhendrickson/foundation
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/markmhendrickson/foundation/fix-feature-bug
Any agent
npx skills add markmhendrickson/foundation --skill fix-feature-bug
Clone the repo
git clone --depth 1 https://github.com/markmhendrickson/foundation

Made for: Claude Code, Codex, Cursor.

Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 750 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 92% copy Near-identical to another mod 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.00017 $0.00750
Opus 5 $0.00009 $0.00375
Sonnet 5 $0.00003 $0.00150
Haiku 4.5 $0.00002 $0.00075

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

Security

Grade A, and why

fix-feature-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 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.

Origin

This is a copy

92% identical to fix-feature-bug — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.cursor/skills/fix-feature-bug/SKILL.md · 101 lines

How it starts

The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Fix Feature Bug

Fix a bug in a feature or module.

Configuration is read from foundation-config.yaml.

This workflow can also be triggered automatically via .cursor/rules/bug_fix_detection.md (or foundation/agent_instructions/cursor_rules/bug_fix_detection.md) when you mention bug/error-related patterns in natural language (e.g., "bug", "error", "fix", "broken"). Both paths execute the same workflow.

Workflow

  1. Load configuration:

    • Read foundation-config.yaml for bug fix settings
    • Check if error classification is configured
    • Determine feature/module directory structure

  2. Identify feature/module from error, path, or context.

  3. Load relevant documents:

    • Repository navigation guide (if configured)
    • Feature/module spec and manifest (if available)
    • Error classification documentation (if configured)
    • Relevant subsystem/module documentation (if configured)

  4. Classify bug (if error classification configured):

    • Use configured error classification system
    • Determine correction approach based on class

  5. Apply correction rules:

    • If Class 1 (Implementation bug): Patch code only
    • If Class 2 (Spec bug): Update spec/manifest first, then align code/tests
    • If Class 3 (Architectural bug): Update subsystem/architecture docs first, then rebuild
    • If no classification: Fix bug and update relevant documentation

  6. Always add a regression test.

  7. Run tests:

    • Run configured test commands
    • Verify fix doesn't break existing functionality

  8. Output:

    • Error class (if classification configured)
    • Reason for classification
    • Corrected files
    • Tests added/updated

Error Classification (Configurable)

If development.bug_fix.error_classification.enabled: true in foundation-config:

  • Class 1: Implementation bug - spec is correct, code doesn't match spec
    • Action: Patch code only
  • Class 2: Spec bug - spec is incomplete or wrong, code matches spec but spec is wrong
    • Action: Update spec/manifest first, then align code/tests
  • Class 3: Architectural bug - subsystem/architecture docs are wrong or incomplete
    • Action: Update architecture docs first, then rebuild

Read the full file on GitHub · 101 lines

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 · 101 lines · 17 tokens per session scan A 76aea90259f6

Subscribe to this mod's changes

fix-feature-bug is a skill published in the GitHub repository markmhendrickson/foundation (2 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 750 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to fix-feature-bug, differing in 9 lines, and is treated as a copy.

Debugging
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens