agentmods.dev

debug

debug is a skill for Claude Code from nicodiansk/turbocharge. It costs 33 tokens per session (1,500 once invoked), scanned A, original, MIT.

A systematic debugging guide for bugs, failed tests, and unexpected behavior. It requires investigating the evidence and finding the root cause before proposing a fix.

In plain words
What is it for?
Use it to read errors and stack traces, reproduce failures, inspect recent changes, and trace problems across component boundaries.
Why use it?
It prevents guess-and-check patches that hide the real problem or create new ones.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the turbocharge plugin — 9 skills, 6 agents, 3 hooks shipped together

not rated 3repo 7d ago A scan 33 tokens original MIT

Good fit Use it to read errors and stack traces, reproduce failures, inspect recent changes, and trace problems across component boundaries.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nicodiansk/turbocharge/debug
View source ↗ nicodiansk/turbocharge
Install

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.

Any agent
npx skills add nicodiansk/turbocharge --skill debug
Clone the repo
git clone --depth 1 https://github.com/nicodiansk/turbocharge

Made for: Claude Code.

Or install turbocharge, the plugin that ships this one along with the rest of its 9 skills, 6 agents, 3 hooks.

Wrote 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.

agentmods badge for debug

README.md
[![agentmods](https://agentmods.dev/badge/skills/nicodiansk/turbocharge/debug/github.svg)](https://agentmods.dev/skills/nicodiansk/turbocharge/debug)
Your own site
<a href="https://agentmods.dev/skills/nicodiansk/turbocharge/debug"><img src="https://agentmods.dev/badge/skills/nicodiansk/turbocharge/debug/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.

agentmods 80×15 button for debug

Your own site · 80×15
<a href="https://agentmods.dev/skills/nicodiansk/turbocharge/debug"><img src="https://agentmods.dev/badge/skills/nicodiansk/turbocharge/debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,500 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.01500
Opus 5.5 $0.00013 $0.00600
Sonnet 5.5 $0.00007 $0.00300
Haiku 4.5 $0.00003 $0.00150

Measured 1mo ago against content hash a994226c2c8f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

debug 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 1mo ago.

The scan reads SKILL.md. This mod also ships 2 executable files (condition-based-waiting-example.ts, find-polluter.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/debug/SKILL.md · 206 lines

How it starts

The opening of the file, as written. The whole thing — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Systematic Debugging

Overview

Random fixes waste time and create new bugs. Quick patches mask underlying issues.

Core principle: ALWAYS find root cause before attempting fixes. Symptom fixes are failure.

Violating the letter of this process is violating the spirit of debugging.

The Iron Law

NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST

If you haven't completed Phase 1, you cannot propose fixes.

The Four Phases

You MUST complete each phase before proceeding to the next.

Phase 1: Root Cause Investigation

BEFORE attempting ANY fix:

  1. Read Error Messages Carefully

    • Don't skip past errors or warnings
    • They often contain the exact solution
    • Read stack traces completely
    • Note line numbers, file paths, error codes

  2. Reproduce Consistently

    • Can you trigger it reliably?
    • What are the exact steps?
    • Does it happen every time?
    • If not reproducible → gather more data, don't guess

  3. Check Recent Changes

    • What changed that could cause this?
    • Git diff, recent commits
    • New dependencies, config changes
    • Environmental differences

  4. Gather Evidence at Component Boundaries For multi-component systems: log what enters and exits each component. Run once to find WHERE it breaks, then investigate that specific component.

  5. Trace Data Flow

    WHEN error is deep in call stack:

    See root-cause-tracing.md in this directory for the complete backward tracing technique.

    Quick version:

    • Where does bad value originate?
    • What called this with bad value?
    • Keep tracing up until you find the source
    • Fix at source, not at symptom

Phase 2: Pattern Analysis

Find the pattern before fixing:

  1. Find Working Examples

    • Locate similar working code in same codebase
    • What works that's similar to what's broken?

  2. Compare Against References

    • If implementing pattern, read reference implementation COMPLETELY
    • Don't skim - read every line
    • Understand the pattern fully before applying

Read the full file on GitHub · 206 lines

Files

What ships with it

5 files 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.

Changes

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.

  1. 1mo ago First seen · 206 lines · 33 tokens per session scan A a994226c2c8f

Subscribe to this mod's changes

debug is a skill published in the GitHub repository nicodiansk/turbocharge (3 stars, last pushed 7d ago), licensed MIT. It adds 33 tokens to every session and 1,500 once invoked, about $0.0001 per session on Opus 5.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.

Debuggingaiai-agentsanthropicartificial-intelligenceclaudeclaude-agent-sdk
Related

Other skills, from other repositories

smart-explore

Token-optimized structural code search using tree-sitter AST parsing. Use instead of reading full files when you need to understand code structure, find functions, or explore a codebase efficiently.

thedotmack/claude-mem · 41 tokens

hivemind-graph

Query the local code graph (functions, classes, calls, imports) through the Deeplake mount at memory/graph/. Use when the user asks structural questions about the codebase — "what calls X?", "what does Y import?", "where is Z defined?", "what's the architecture / which subsystems exist?", "what's the impact of…

activeloopai/hivemind · 105 tokens

dejavu-scan

Trigger a manual scan for antipatterns. Use when user asks "scan for patterns", "dejavu scan", "check for mistakes".

cmg8431/claude-dejavu · 33 tokens

dejavu-status

Quick status check for dejavu. Use when user asks "dejavu status", "how's dejavu doing".

cmg8431/claude-dejavu · 27 tokens

compile-status

Show pending changes and LLM-powered impact analysis without compiling. Detects new/modified/deleted sources via content hashing, maps them to dirty buckets, reads changed sources to assess impact and detect contradictions with existing claims. Use to preview what incremental compilation would do before running it.

chappyasel/meta-kb · 58 tokens

weekly-digests

Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests"…

thedotmack/claude-mem · 93 tokens