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/viknesh20-20/claude-code-tool-kit/debugnpx skills add viknesh20-20/claude-code-tool-kit --skill debuggit clone --depth 1 https://github.com/viknesh20-20/claude-code-tool-kitWhat 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.00036 | $0.00792 |
| Opus 5 | $0.00018 | $0.00396 |
| Sonnet 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 2d 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.
- 2d 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 4mo ago), licensed MIT. It adds 36 tokens to every session and 792 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
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
security-review
Review trust boundaries, auth/authz, injection, secrets, filesystem/network exposure, dependencies, and exploitability without pretending a shallow lint is an audit.
ppt-review
Read this skill only after current officereview structural output and relevant rendered images exist. Do not use source code, a tool success flag, or the first-slide preview as a substitute for deck evidence.
ui-design-contract
Use this skill before rendering when the direction must persist across multiple screens/components, brand or system work, conflicting references, formal handoff, or a genuinely vague visual system. Ordinary single-screen screenshots and clear briefs use ui-design-executor's compact source/visual thesis instead of…
helmor-debug-operate
Operate, reproduce, and debug a running local Helmor desktop development build through the Tauri MCP bridge. Use when the user asks to use Tauri MCP, towery MCP, the local dev build, the Tauri webview, visual end-to-end validation, UI automation, screenshots, DOM/accessibility snapshots, IPC or log tracing…