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/u9401066/rootcause-mcp/bug-fixnpx skills add u9401066/rootcause-mcp --skill bug-fixgit clone --depth 1 https://github.com/u9401066/rootcause-mcpWrote 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/u9401066/rootcause-mcp/bug-fix)<a href="https://agentmods.dev/skills/u9401066/rootcause-mcp/bug-fix"><img src="https://agentmods.dev/badge/skills/u9401066/rootcause-mcp/bug-fix.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01489 |
| Opus 5 | $0.00000 | $0.00745 |
| Sonnet 5 | $0.00000 | $0.00298 |
| Haiku 4.5 | $0.00000 | $0.00149 |
Grade A, and why
bug-fix 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.
This is a copy
100% identical to bug-fix — 0 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.
How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug 修復工作流
描述
結構化的 Bug 修復流程，包含根因分析和回歸測試。
觸發條件
- 「修 bug」「fix bug」「除錯」
- 「BF: [問題描述]」
🐛 Bug 修復流程
┌─────────────────────────────────────────────────────────────┐
│ Bug Fix Workflow │
├─────────────────────────────────────────────────────────────┤
│ Step 1: 🔍 重現 (Reproduce) │
│ ├─ 確認重現步驟 │
│ ├─ 收集錯誤訊息/日誌 │
│ └─ 建立最小重現案例 │
├─────────────────────────────────────────────────────────────┤
│ Step 2: 🎯 定位 (Locate) │
│ ├─ 分析錯誤堆疊 │
│ ├─ 追蹤程式碼路徑 │
│ └─ 識別問題根因 │
├─────────────────────────────────────────────────────────────┤
│ Step 3: 🧪 測試先行 (Test First) │
│ ├─ 撰寫失敗的測試案例 │
│ ├─ 確認測試能重現問題 │
│ └─ 這將成為回歸測試 │
├─────────────────────────────────────────────────────────────┤
│ Step 4: 🔧 修復 (Fix) │
│ ├─ 實施修復 │
│ ├─ 最小化變更範圍 │
│ └─ 確認測試通過 │
├─────────────────────────────────────────────────────────────┤
│ Step 5: ✅ 驗證 (Verify) │
│ ├─ 執行完整測試套件 │
│ ├─ 檢查是否引入新問題 │
│ └─ [code-reviewer] 審查修復 │
├─────────────────────────────────────────────────────────────┤
│ Step 6: 📝 記錄 (Document) │
│ ├─ 更新 Memory Bank │
│ ├─ 記錄根因分析 │
│ └─ 更新相關文檔 │
└─────────────────────────────────────────────────────────────┘
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.
- 3d ago First seen · 171 lines · 0 tokens per session scan A fa0c0d0b3d5c
bug-fix is a skill published in the GitHub repository u9401066/rootcause-mcp (0 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,489 tokens. A static security scan graded it A with 0 findings. It is 100% identical to bug-fix, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
bug-fix
Structured bug fixing workflow with root cause analysis and regression prevention. Triggers: BF, 修 bug, fix bug, debug, 除錯, 錯誤, error, 問題, issue, 修復, fix, 故障, fault, 異常, exception, 失敗, failure, 不能用, broken, 壞掉.
code-review-workflow
Complete code review workflow for PR/MR with multiple reviewers and automated checks. Triggers: PRW, 審查流程, review workflow, PR review, MR review, pull request, merge request, 程式碼審查流程, full review, 完整審查.
release
Version release preparation workflow including changelog, version bump, and deployment checks. Triggers: REL, release, 發布, 版本發布, deploy, 部署, publish, 上線, ship, tag, 打標籤, 版本, version bump, 升版.
sop-mcp-usage
How to use the SOP-MCP server to execute, create, and improve Standard Operating Procedures.
feature-development
Complete feature development workflow orchestrating multiple skills from planning to deployment. Triggers: FD, 新功能, 開發功能, feature, implement, 實作, 實現, 建立功能, create feature, develop, 開發新, add feature, 加功能, 功能開發.
git-precommit
Orchestrate pre-commit workflow including Memory Bank sync, README/CHANGELOG/ROADMAP updates. Triggers: GIT, gc, push, commit, 提交, 準備 commit, 要提交了, git commit, pre-commit, 推送, stage, 暫存, checkin, 簽入, submit, save, 準備發布, ready to commit, 要推了.