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/rootsli/claude-quickstart-cn/debug-helpernpx skills add rootsli/claude-quickstart-cn --skill debug-helpergit clone --depth 1 https://github.com/rootsli/claude-quickstart-cnWrote 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/rootsli/claude-quickstart-cn/debug-helper)<a href="https://agentmods.dev/skills/rootsli/claude-quickstart-cn/debug-helper"><img src="https://agentmods.dev/badge/skills/rootsli/claude-quickstart-cn/debug-helper.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.00022 | $0.00976 |
| Opus 5 | $0.00011 | $0.00488 |
| Sonnet 5 | $0.00004 | $0.00195 |
| Haiku 4.5 | $0.00002 | $0.00098 |
Grade A, and why
debug-helper 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 4d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Helper
帮助调试代码，分析错误信息，定位问题根源，提供修复建议。
什么时候使用
当用户请求以下操作时使用此 skill：
- 调试代码
- 分析错误信息
- 修复 bug
- 理解异常原因
- 排查问题
操作说明
调试步骤
- 收集信息 - 获取错误信息、堆栈跟踪、相关代码
- 分析错误 - 理解错误类型和消息含义
- 定位根源 - 找到导致问题的代码位置
- 提供解决方案 - 给出具体的修复建议
- 预防建议 - 提供避免类似问题的建议
常见错误类型
| 错误类型 | 可能原因 |
|---|---|
| TypeError | 类型不匹配、空值操作 |
| ReferenceError | 未定义变量、作用域问题 |
| SyntaxError | 语法错误、缺少括号/引号 |
| RuntimeError | 运行时逻辑错误 |
| NetworkError | 网络请求失败、超时 |
分析框架
对于每个错误，需要分析：
- What: 发生了什么错误
- Where: 错误发生在哪里
- Why: 为什么会发生
- How: 如何修复
输出格式
- 使用
templates/debug-report.md模板格式化输出。 - 优先使用简体中文输出。
## 调试分析报告
### 错误概述
[错误类型和简要描述]
### 根本原因
[详细分析]
### 修复方案
[具体代码修改]
### 预防建议
[如何避免类似问题]
示例
输入
错误信息：
TypeError: Cannot read properties of undefined (reading 'map')
at UserList (UserList.jsx:15:23)
at renderWithHooks (react-dom.development.js:14985:18)
相关代码：
function UserList({ users }) {
return (
<ul>
{users.map(user => (
<li key={user.id}>{user.name}</li>
))}
</ul>
);
}
输出
调试分析报告
错误概述
TypeError: Cannot read properties of undefined (reading 'map')
在 UserList 组件第 15 行调用 .map() 时，users 变量为 undefined。
根本原因
- 直接原因: 尝试在
undefined上调用.map()方法 - 深层原因:
- 父组件可能没有传递
usersprop - 数据获取尚未完成时组件已渲染
- API 返回格式与预期不符
- 父组件可能没有传递
修复方案
方案 1: 添加默认值（推荐）
function UserList({ users = [] }) {
return (
<ul>
{users.map(user => (
<li key={user.id}>{user.name}</li>
))}
</ul>
);
}
方案 2: 条件渲染
function UserList({ users }) {
if (!users || users.length === 0) {
return <p>No users found</p>;
}
return (
<ul>
{users.map(user => (
<li key={user.id}>{user.name}</li>
))}
</ul>
);
}
方案 3: 可选链操作符
function UserList({ users }) {
return (
<ul>
{users?.map(user => (
<li key={user.id}>{user.name}</li>
))}
</ul>
);
}
What ships with it
1 file 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.
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.
- 4d ago First seen · 172 lines · 22 tokens per session scan A 00eeef6963e5
debug-helper is a skill published in the GitHub repository rootsli/claude-quickstart-cn (10 stars, last pushed 1mo ago), licensed CC0-1.0. It adds 22 tokens to every session and 976 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…