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 skills add u9401066/template-is-all-you-need --skill bug-fixgit clone --depth 1 https://github.com/u9401066/template-is-all-you-needWrote 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/template-is-all-you-need/bug-fix)<a href="https://agentmods.dev/skills/u9401066/template-is-all-you-need/bug-fix"><img src="https://agentmods.dev/badge/skills/u9401066/template-is-all-you-need/bug-fix/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/u9401066/template-is-all-you-need/bug-fix"><img src="https://agentmods.dev/badge/skills/u9401066/template-is-all-you-need/bug-fix.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00080 | $0.01489 |
| Opus 5 | $0.00040 | $0.00745 |
| Sonnet 5 | $0.00016 | $0.00298 |
| Haiku 4.5 | $0.00008 | $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 10d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- bug-fix — 100% identical, 0 lines differ
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.
- 10d ago First seen · 171 lines · 0 tokens per session scan A fa0c0d0b3d5c
bug-fix is a skill published in the GitHub repository u9401066/template-is-all-you-need (3 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 80 tokens to every session and 1,489 once invoked, about $0.0004 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.
Other skills, from other repositories
extracting-code-structure
Use when listing all methods, functions, or classes in a file, exploring unfamiliar code, getting API overviews, or deciding what to read selectively without loading entire files.
analyzing-code-structure
Use when editing code structure with text matching ambiguity, handling "oldstring not unique" problems, or performing formatting-independent pattern matching across function signatures, method calls, and class structures.
investigating-builds
Use when the user is working with an existing Buildkite CI run and wants to understand, diagnose, or act on it. Strong signals: a buildkite.com URL, the word "buildkite", the bk CLI, the bktide tool, or a reference to a specific pipeline, build, or job. Covers intents like: "why did this build fail", "what's flaking"…
absolute-debt
Lint and typecheck debt paydown: clear pre-existing repo-wide lint/type violations and suppressions (@ts-ignore, # type: ignore) one rule per wave, fixing causes not symptoms. Runs on green main. For diff-scoped quality use absolute-simplify. Triggers on "absolute debt", "fix our lint warnings", "clear the type…
absolute-deflake
Flaky test fixes: detect nondeterministic tests empirically (repeat/shuffle/parallel runs), diagnose the root cause, fix it — never retry/skip/sleep — and verify across many randomized runs. Triggers on "absolute deflake", "fix flaky tests", "CI is flaky", "this test fails randomly/intermittently".
absolute-prune
Dead code and dependency cleanup, repo-wide: unused deps, unreferenced exports, unreachable code, orphaned files — removed only with tool evidence, in reversible waves. Runs on green main. For diff-scoped cleanup use absolute-simplify. Triggers on "absolute prune", "remove dead code", "find unused deps/exports", "what…