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 forest6511/claude-code-recipes-v2 --skill debug-skillsgit clone --depth 1 https://github.com/forest6511/claude-code-recipes-v2Wrote 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/forest6511/claude-code-recipes-v2/debug-skills)<a href="https://agentmods.dev/skills/forest6511/claude-code-recipes-v2/debug-skills"><img src="https://agentmods.dev/badge/skills/forest6511/claude-code-recipes-v2/debug-skills.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.1 | $0.00031 | $0.00424 |
| Opus 5 | $0.00015 | $0.00212 |
| Sonnet 5 | $0.00006 | $0.00085 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
debug-skills 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 7d 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
Skillsデバッグチェックリスト
以下の手順で問題を特定してください。
チェック1: 手動呼び出しの確認
/skill-name で手動呼び出しが成功するか?
-> 失敗: SKILL.mdの内容を確認（チェック5, 6へ）
-> 成功: descriptionの問題（チェック2へ）
チェック2: バジェット超過の確認
/context で除外警告が出ていないか?
-> 警告あり: バジェット超過（レシピ50参照）
-> 警告なし: チェック3へ
チェック3: descriptionのトリガー条件
descriptionに具体的なトリガー条件があるか? -> なし: "Use when..." を追加 -> あり: チェック4へ
チェック4: context:forkの適切性
context: fork を使っていて、明確なタスクがあるか? -> タスクなし: context:forkを削除するか、タスクを追加 -> タスクあり: チェック5へ
チェック5: YAML構文の検証
フロントマターにYAML構文エラーがないか? -> コロン(:)を含む値はクォートで囲む -> インデントは半角スペース2つ
チェック6: nameフィールドの制約
nameが制約を満たしているか? -> 小文字、数字、ハイフンのみ -> 最大64文字 -> 大文字、アンダースコアは不可
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.
- 7d ago First seen · 49 lines · 31 tokens per session scan A 0b8b4780cb8d
debug-skills is a skill published in the GitHub repository forest6511/claude-code-recipes-v2 (5 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 424 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-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.