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 viknesh20-20/claude-code-tool-kit --skill debuggit clone --depth 1 https://github.com/viknesh20-20/claude-code-tool-kitWrote 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/viknesh20-20/claude-code-tool-kit/debug)<a href="https://agentmods.dev/skills/viknesh20-20/claude-code-tool-kit/debug"><img src="https://agentmods.dev/badge/skills/viknesh20-20/claude-code-tool-kit/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.
<a href="https://agentmods.dev/skills/viknesh20-20/claude-code-tool-kit/debug"><img src="https://agentmods.dev/badge/skills/viknesh20-20/claude-code-tool-kit/debug.svg" alt="Reviewed on agentmods" width="80" 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.00036 | $0.00792 |
| Opus 5.5 | $0.00014 | $0.00317 |
| Sonnet 5.5 | $0.00007 | $0.00158 |
| Haiku 4.5 | $0.00004 | $0.00079 |
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.
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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Structured Debugging
Recent Changes
!git log --oneline -10 2>/dev/null
!git diff --stat HEAD~3 2>/dev/null
Debugging Process
Step 1: Gather Information
- What is the symptom? — Error message, unexpected behavior, crash, performance issue
- When did it start? — Check recent commits:
git log --oneline -20 - Is it reproducible? — Always, sometimes, only in certain environments?
- What changed? — Recent code changes, dependency updates, config changes
Step 2: Read the Error
If there's an error message or stack trace:
- Read the full error message — don't skip parts
- Identify the origin — which file and line threw the error?
- Trace the call stack — how did execution reach that point?
- Check for root cause vs symptom — the first error in the chain is usually the cause
Step 3: Isolate the Problem
Use a binary search strategy:
- Narrow the scope: Is the issue in the frontend, backend, database, or external service?
- Check inputs: Are the inputs to the failing function correct?
- Check dependencies: Are all required services/modules available?
- Check state: Is the application/database in the expected state?
- Check environment: Are env vars, configs, and versions correct?
Step 4: Common Debugging Patterns
"It works on my machine"
- Check environment variables
- Check dependency versions (lock file differences)
- Check OS/runtime version differences
- Check file path separators (Windows vs Unix)
- Check timezone/locale differences
"It worked yesterday"
git bisectto find the breaking commit- Check for dependency updates (lock file changes)
- Check for infrastructure/config changes
- Check for data changes in the database
"It works sometimes"
- Race condition — look for shared mutable state
- Timing issue — look for missing awaits, unhandled promises
- Resource exhaustion — connections, file handles, memory
- External dependency flakiness — network, API rate limits
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.
- 1mo ago First seen · 89 lines · 36 tokens per session scan A a1c387254c5e
debug is a skill published in the GitHub repository viknesh20-20/claude-code-tool-kit (7 stars, last pushed 5mo ago), licensed MIT. It adds 36 tokens to every session and 792 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.
Other skills, from other repositories
rust-check
Run cargo check on the current Rust project to find compile errors.
debug
Reproduce, minimize, localize, identify root cause, and distinguish diagnosis from an authorized fix. Prefer root-cause over symptom patches.
feedback
Skill "feedback" from Hmbown/Codewhale, covering feedback, when to use, setup, workflow and non-goals.
developing-openrig
Use when changing OpenRig's own source in a clone of the openrig repository: finding which package or file owns a behaviour, choosing which tests to run, testing a change without disturbing the OpenRig daemon your own session runs on, judging whether a diff touches a high-risk area, or preparing a pull request. Not…
postmortem
Auto-generates a structured postmortem from a completed campaign. Reads the campaign file, telemetry logs, and feature ledger. Produces a documented analysis of what broke, what the safety systems caught, and what patterns emerged. Can also be invoked manually for any incident.
systematic-debugging
4-phase root cause analysis: observe, hypothesize, verify, fix. Enforces investigation before any code changes. Emergency stop after 2 failed fixes. Prevents shotgun debugging and fix cascades.