agentmods.dev

fix-feature-bug

A guided process for investigating and fixing software bugs, including failures reported by tests or error messages. It asks for confirmation, identifies the affected feature, and checks the fix with a regression test—a test that prevents the same problem from returning.

In plain words
What is it for?
It helps diagnose errors, locate the affected code, reproduce and fix broken features, classify failures, add regression tests, and report what changed.
Why use it?
It turns a vague report that something is broken into a repeatable investigation and makes the fix easier to verify. It also helps catch related problems before the change is considered complete.

Skill for Claude CodeCodex

5 5d ago A scan 57 tokens original MIT
View the source file markmhendrickson/ateles
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/ateles/fix-feature-bug
Any agent
npx skills add markmhendrickson/ateles --skill fix-feature-bug
Clone the repo
git clone --depth 1 https://github.com/markmhendrickson/ateles

Made for: Claude Code, Codex.

Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 998 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.00057 $0.00998
Opus 5 $0.00028 $0.00499
Sonnet 5 $0.00011 $0.00200
Haiku 4.5 $0.00006 $0.00100

Measured 3d ago against content hash cc5c66117989, 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 3d 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.

.claude/skills/fix-feature-bug/SKILL.md · 120 lines

How it starts

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

Fix Feature Bug

Systematically fix bugs using error classification and regression testing.

When to Use

Use this skill when:

  • User mentions "bug", "error", "fix", "broken", "not working", "failing"
  • User reports "issue" or "problem" in context of code/functionality
  • Error messages or stack traces are present
  • Test failures mentioned
  • User mentions "regression" or "broken feature"
  • User explicitly invokes /fix-feature-bug

Workflow

Step 1: Detection and Confirmation

  1. Extract bug information from context:

    • Error messages or stack traces (if provided)
    • Feature/module ID (if mentioned or inferred from paths)
    • Description of the problem
    • Steps to reproduce (if mentioned)

  2. Identify affected feature/module:

    • Check error messages for file paths
    • Check context for feature mentions
    • Check open files for feature references
    • If cannot identify → ask: "Which feature/module is affected? (identifier or 'unknown')"

  3. Ask for confirmation:

    I see you're reporting a bug. Should I fix this using the bug fix workflow? 
Feature/Module: {identifier} (or 'unknown' if not identified)
(yes/no)

  4. Handle exceptions:

    • If user says "no" → do not proceed
    • If user says "just document it" → document the bug instead of fixing

Step 2: Execute Bug Fix Workflow

If user confirms (yes):

  1. Load configuration:

    • Read foundation-config.yaml for bug fix workflow settings
    • Check if development.bug_fix.error_classification.enabled is true
    • Determine feature unit directory (if feature units enabled)

  2. Load required documents:

    • foundation/agent_instructions/cursor_commands/fix_feature_bug.md — workflow
    • Repository navigation guide (if configured)
    • Feature spec and manifest (if feature units enabled and identifier provided)
    • Error classification documentation (if configured)
    • Relevant subsystem/module docs (if configured)

  3. Classify bug (if error classification configured):

    • Class 1: Implementation bug (spec correct, code wrong) → Patch code only
    • Class 2: Spec bug (code correct, spec wrong) → Update spec first, then align code
    • Class 3: Architectural bug (architecture docs wrong) → Update architecture docs first

Read the full file on GitHub · 120 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. 3d ago First seen · 120 lines · 57 tokens per session scan A cc5c66117989

Subscribe to this mod's changes

fix-feature-bug is a skill published in the GitHub repository markmhendrickson/ateles (5 stars, last pushed 5d ago), licensed MIT. It adds 57 tokens to every session and 998 once invoked, about $0.0003 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.

Autonomous AgentsDebuggingLLMaauthagent-swarmai-agentsclaude
Related

Other skills, from other repositories

10x-orchestrator

MANDATORY - The core brain of 10X Vibe Marketer. You are the autonomous CMO orchestrating a full marketing agency of 12 specialist departments. Load this skill for ANY marketing task - content creation, SEO, campaigns, strategy, research, analytics, outreach, social media, email, paid ads, branding, funnel…

OpenAnalystInc/Vibe-Marketer · 91 tokens

10x-setup

First-time setup and initialization for 10X Vibe Marketer. Includes an interactive wizard that lets users choose their database, features, marketing focus, visual tools, and tracking preferences. Checks setup.log to determine if setup has already been completed. Run via /setup or auto-triggered on first use.

OpenAnalystInc/Vibe-Marketer · 66 tokens

10x-visualizer

Generate visual marketing deliverables — strategy boards, funnel diagrams, flowcharts, journey maps, dashboards, and more — using TLDraw SDK (local .tldr files). Each department agent creates visuals for their own domain. Invoke with /report.

OpenAnalystInc/Vibe-Marketer · 55 tokens

community-manager

Skill "community-manager" from OpenAnalystInc/Vibe-Marketer, covering community manager — 10x vibe marketer, identity, step-by-step execution, cli visual identity and expertise.

OpenAnalystInc/Vibe-Marketer · 0 tokens

10x-research

The research orchestration engine for 10X Vibe Marketer. Powers multi-platform, real-time research across 13 platforms using Claude in Chrome and WebSearch/WebFetch. Spawns platform-specific research agents in parallel, consolidates findings through the research lead, and delivers actionable marketing intelligence.

OpenAnalystInc/Vibe-Marketer · 0 tokens

affiliate-specialist

Skill "affiliate-specialist" from OpenAnalystInc/Vibe-Marketer, covering affiliate specialist — 10x vibe marketer, identity, step-by-step execution, cli visual identity and expertise.

OpenAnalystInc/Vibe-Marketer · 0 tokens