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/jerrylookupu/klein-harness/systematic-debuggingnpx skills add JerryLookupU/klein-harness --skill systematic-debugginggit clone --depth 1 https://github.com/JerryLookupU/klein-harnessWrote 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/jerrylookupu/klein-harness/systematic-debugging)<a href="https://agentmods.dev/skills/jerrylookupu/klein-harness/systematic-debugging"><img src="https://agentmods.dev/badge/skills/jerrylookupu/klein-harness/systematic-debugging.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.00049 | $0.00712 |
| Opus 5 | $0.00024 | $0.00356 |
| Sonnet 5 | $0.00010 | $0.00142 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
systematic-debugging 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 5d 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.
What it actually says
This Skill Is For
这个 skill 用于：
- bug 报告
- 回归
- error / exception / traceback
- “为什么坏了”
- “哪里出问题了”
- 修复前必须先找根因的场景
一句话：
先证明原因，再决定修法。
核心纪律
- 不先给 quick fix
- 不同时堆多个假设
- 不在没有证据时猜原因
- 不在没有复现或等价失败证据时宣称已经定位
- 不把“大改一轮看看”当作调试
最小工作流
1. 写清楚现象
至少明确：
- 观察到的错误或异常行为
- 期望行为
- 影响范围
- 当前已知输入 / 环境 / 前提
2. 先取证
优先收集：
- 完整错误信息
- 日志 / trace / verify 输出
- 最近相关改动
- 相关配置和输入数据
如果拿不到完整复现，也要先拿到最接近的失败证据。
3. 尝试复现
- 给出最小复现步骤
- 如果不能稳定复现，写明阻塞点和替代证据
- 区分“真实未复现”与“尚未验证”
4. 缩成单一假设
一次只保留一个当前主假设：
- 这个假设解释了什么现象
- 哪条证据支持它
- 什么最小检查可以证伪它
5. 运行最小判别测试
- 优先选能区分假设真假的最小动作
- 不要一上来就大面积修改代码
- 如果测试推翻假设，回到上一步换下一个假设
6. 只有确认原因后才允许修复
修复方案必须满足：
- 与已确认原因直接对应
- 改动面尽可能小
- 有明确验证方法
- 能说明为什么不会引入更大回归
7. 修复后再验证
至少验证：
- 原问题不再出现
- 相关回归面没有被打坏
- 结论有命令输出、日志或文件证据支撑
交付格式
调试结论至少包含：
ObservedExpectedEvidenceHypothesisDisprover/TestConfirmed Cause或Still UnconfirmedMinimal FixVerification
退出条件
只有在以下任一成立时才允许离开调试模式：
- 根因已确认，且最小修复与验证路径明确
- 当前证据不足，已清楚记录缺口和下一步取证动作
“看起来像是这里”不算完成。
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.
- 5d ago First seen · 110 lines · 49 tokens per session scan A 48b7b6415b13
systematic-debugging is a skill published in the GitHub repository JerryLookupU/klein-harness (11 stars, last pushed 5mo ago), licensed MIT. It adds 49 tokens to every session and 712 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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.
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…