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 JackyST0/awesome-agent-skills --skill debug-helpergit clone --depth 1 https://github.com/JackyST0/awesome-agent-skillsWrote 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/jackyst0/awesome-agent-skills/debug-helper)<a href="https://agentmods.dev/skills/jackyst0/awesome-agent-skills/debug-helper"><img src="https://agentmods.dev/badge/skills/jackyst0/awesome-agent-skills/debug-helper.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00020 | $0.01051 |
| Opus 5 | $0.00010 | $0.00526 |
| Sonnet 5 | $0.00004 | $0.00210 |
| Haiku 4.5 | $0.00002 | $0.00105 |
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 9d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Helper
帮助调试代码,分析错误信息,定位问题根源,提供修复建议。
Help debug code by analyzing error messages, identifying root causes, and providing fix suggestions.
When to Use
当用户请求以下操作时使用此 skill:
- 调试代码 / Debug code
- 分析错误信息 / Analyze error messages
- 修复 bug / Fix bugs
- 理解异常原因 / Understand exception causes
- 排查问题 / Troubleshoot issues
Instructions
调试步骤 / Debugging Steps
- 收集信息 - 获取错误信息、堆栈跟踪、相关代码
- 分析错误 - 理解错误类型和消息含义
- 定位根源 - 找到导致问题的代码位置
- 提供解决方案 - 给出具体的修复建议
- 预防建议 - 提供避免类似问题的建议
常见错误类型 / Common Error Types
| 错误类型 | 可能原因 |
|---|---|
| TypeError | 类型不匹配、空值操作 |
| ReferenceError | 未定义变量、作用域问题 |
| SyntaxError | 语法错误、缺少括号/引号 |
| RuntimeError | 运行时逻辑错误 |
| NetworkError | 网络请求失败、超时 |
分析框架 / Analysis Framework
对于每个错误,需要分析:
- What: 发生了什么错误
- Where: 错误发生在哪里
- Why: 为什么会发生
- How: 如何修复
输出格式 / Output Format
使用 templates/debug-report.md 模板格式化输出。
Use the templates/debug-report.md template to format output.
## 调试分析报告 / Debug Analysis Report
### 错误概述 / Error Summary
[错误类型和简要描述]
### 根本原因 / Root Cause
[详细分析]
### 修复方案 / Fix
[具体代码修改]
### 预防建议 / Prevention
[如何避免类似问题]
Examples
输入 / Input
错误信息:
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>
);
}
输出 / Output
调试分析报告
错误概述
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>
);
}
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.
- 9d ago First seen · 176 lines · 20 tokens per session scan A 97fb195026aa
debug-helper is a skill published in the GitHub repository JackyST0/awesome-agent-skills (632 stars, last pushed today), licensed CC0-1.0. It adds 20 tokens to every session and 1,051 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-30.
Other skills, from other repositories
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
issue-root-resolution
Trigger: root audit, atacar la raíz, issue roots, backlog roots, mechanism map, deletion-driven fix, resolver issues de raíz, close outdated issues. Audit and resolve issue clusters by verified root cause.
rdd-defect-workflow
Trigger: RDD, receipt-driven development, review authority, receipt/lineage, correction/recovery, delivery gate/kill switch, bounded review defects. Guide work.
debug-live
Guides root-cause investigations with debugging capabilities by setting breakpoints, starting a debug session, stepping through execution, inspecting variables, and tracing symptoms back to their origin. Prefer it for runtime bugs, failing tests, exceptions, crashes, hangs, wrong/null values, and unexpected output…
post-mortem
Diagnose instruction defects and optionally submit Rosetta GitHub issue.
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.