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 agentmods add skills/zxpmail/reqforge/bug-fixernpx skills add zxpmail/ReqForge --skill bug-fixergit clone --depth 1 https://github.com/zxpmail/ReqForgeWhat 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 | $0.00000 | $0.02434 |
| Opus 5 | $0.00000 | $0.01217 |
| Sonnet 5 | $0.00000 | $0.00487 |
| Haiku 4.5 | $0.00000 | $0.00243 |
Grade A, and why
bug-fixer 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.
How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: bug-fixer description: Used when the user says "this feature is broken", "getting an error", "something's not right", or reports a bug, compilation error, or runtime exception. Locates root cause through a four-stage systematic debugging process and fixes it. version: 1.2.0 updated: 2026-06-27 requires: []
[Task] Locate the root cause of bugs through a systematic debugging process and fix them. Fix one problem at a time. Assess impact before each modification. Verify regression after fix.
[Invocation Context] bug-fixer may be called in two scenarios: 1. User directly reports a bug -> main Agent invokes bug-fixer -> after fix, suggest user run /code-review to verify 2. code-review finds confirmed bug/security/type issues (confidence_5 ≥ 4, or legacy confidence ≥ 0.6) -> main Agent invokes bug-fixer, passing the failure items from the code-review report -> after fix, main Agent re-dispatches code-review
**Action filter**: bug-fixer receives **only `auto-fix` findings**. Findings with `action="ask-user"` (intent / product-behavior / dead-code decisions) are escalated to the human by dev-builder *before* reaching bug-fixer — never auto-fix them. See `../_shared/finding-actions.md`.
[Not For] - Feature requests or new functionality -> use /dev-builder instead - Code quality or style issues without runtime errors -> use /code-review instead - Performance optimization without a specific bug -> use /code-review with performance dimension
[Dependency Check] Automatically executed as the first step when the Skill starts:
Required:
- Project code exists -> if no code, prompt to call /dev-builder first
- Bug description -> user-provided symptoms, or failure item descriptions from a code-review report
Optional (enhances debugging capability):
- Product-Spec.md -> if available, cross-reference expected behavior to determine if it is a bug or a feature
- DEV-PLAN.md -> if available, locate the relevant Phase and files
- Design tool MCP (Pencil / Figma, etc.) -> if available, cross-reference design to check if UI is correct
- Playwright plugin -> if available, automate reproduction and verification
- git -> if available, use git log/diff/blame to trace changes
- **Dependency Graph** (`dep-graph`) -> if available, run `pnpm dep-graph affected <file>` to scope the blast radius before debugging
- **forge-bug-fix** (`pnpm forge-bug-fix`) -> if available, use diagnose/trace/verify to automate preflight checks, capture debug snapshots, and run post-fix verification
[Shared Discipline]
Karpathy 四原则 → ../_shared/karpathy-discipline.md（bug 场景：先证据后改码；最小修复）
只修 auto-fix finding；ask-user（意图/产品行为/死代码决策）已被上游 escalate → ../_shared/finding-actions.md
[First Principles]
Debug 前必读 references/first-principles.md
[Output Style]
→ references/output-style.md
→ Bug 报告 / 修复完成必须附加 ../_shared/output-status-protocol.md（Status: BLOCKED 或 NEEDS_CONTEXT 时必须说明原因）
[File Structure]
bug-fixer/ ├── SKILL.md ├── commands/bug-fixer.md └── references/ ├── first-principles.md ├── output-style.md ├── debugging-strategy.md # 四阶段（Stage 1–4） ├── cot-diagnostic-checklist.md ├── three-layer-diagnostic-model.md ├── debugging-rule-checklist.md ├── anti-rationalization.md ├── anti-ai-slop-checklist.md # 交付前自检：防敷衍式修 bug ├── workflow.md # Startup → Debug → Verify → Complete └── yolo-mode.md ../_shared/
What ships with it
13 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.
- commands/bug-fixer.md 572 B
- references/anti-ai-slop-checklist.md 3.4 KB
- references/anti-rationalization.md 1.2 KB
- references/cot-diagnostic-checklist.md 560 B
- references/debugging-rule-checklist.md 3.4 KB
- references/debugging-strategy.md 4.5 KB
- references/dimension-checklist.md 3.3 KB
- references/first-principles.md 1.7 KB
- references/output-style.md 1.5 KB
- references/three-layer-diagnostic-model.md 798 B
- references/workflow.md 4.6 KB
- references/yolo-mode.md 452 B
- skill.json 924 B
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.
- 2d ago First seen · 179 lines · 0 tokens per session scan A 34325c75bd0d
bug-fixer is a skill published in the GitHub repository zxpmail/ReqForge (18 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,434 tokens. 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
chinese-documentation
中文文档排版参考——中英文空格、全半角标点、术语保留、链接格式、中文文案排版指北约定。仅在用户显式 /chinese-documentation 时调用，不要根据上下文自动触发。.
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
subagent-driven-development
当在当前会话中执行包含独立任务的实现计划时使用.
orchestration-team
Operating manual for the orchestration pod. Covers lead vs peer roles, monitoring with rig commands, permission handling, implementation pair gating, dogfood loops, review routing, agent behavioral models, intervention discipline, and communication culture.
adr
Create and manage Architecture Decision Records. Documents significant technical decisions with context, alternatives, and consequences. Also supports evaluate (assess proposals) and design (system design) modes.
deploy-checklist
Pre-deployment verification checklist. Generates customized checklists based on tech-stack with rollback triggers. Auto-invoked by /draft:upload.