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 dhaupin/vant --skill vant-skill-debuggergit clone --depth 1 https://github.com/dhaupin/vantWrote 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/dhaupin/vant/vant-skill-debugger)<a href="https://agentmods.dev/skills/dhaupin/vant/vant-skill-debugger"><img src="https://agentmods.dev/badge/skills/dhaupin/vant/vant-skill-debugger/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/dhaupin/vant/vant-skill-debugger"><img src="https://agentmods.dev/badge/skills/dhaupin/vant/vant-skill-debugger.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.00007 | $0.00296 |
| Opus 5.5 | $0.00003 | $0.00118 |
| Sonnet 5.5 | $0.00001 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
debugger 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.
What it actually says
Debugger
Debugging tools.
When To Use
- Bugs to find
- Issues to trace
- Errors to understand
What To Do
1. Start Debugging
| Language | Tool |
|---|---|
| JavaScript | node --inspect |
| Python | -m pdb |
| Go | dlv |
| Rust | rust-gdb |
2. Common Commands
| Command | What |
|---|---|
| break | Set breakpoint |
| continue | Run to next |
| step | Step into |
| next | Step over |
| Print variable | |
| backtrace | Show stack |
3. Breakpoints
// JavaScript
debugger;
// Python
import pdb; pdb.set_trace()
// Go
debugln("here")
4. Inspect
(gdb) print variable
(pdb) pp variable
node inspect
Output
## Debug
| Breakpoint | Hit |
|-----------|-----|
| [n] | [count] |
### Issues Found
- [list]
Role: Debugger
Input: Code + error
Output: Root cause
Find the bug.
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 · 88 lines · 7 tokens per session scan A ba8245cc4ac4
debugger is a skill published in the GitHub repository dhaupin/vant (11 stars, last pushed today), licensed MIT. It adds 7 tokens to every session and 296 once invoked, about $0.0000 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
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
rn-debugging
This skill should be used when the user asks to "debug the app", "fix a crash", "diagnose a blank screen", "read error logs", "troubleshoot CDP connection", "check Metro status", "find native crashes", "inspect network failures", "the app crashed", "I see a blank screen", "the screen is white", "something broke", "app…
python-run
Run and debug Python scripts in the project. Use when the user says "run python", "execute this script", "debug this py file", or wants to run/modify a .py file. Handles dependency checks, linting, execution, and error analysis.
doctor
Explicit Codex workflow: Run strictly read-only Codex plugin, MCP contract, schema, and environment diagnostics; recommend but never execute recovery.
debug-screen
Explicit Codex workflow: Diagnose why the current screen is broken, showing unexpected content, or crashing. Gathers parallel evidence from all layers and applies a targeted fix.
triage-issue
Analyze a GitHub issue, verify claims against the codebase, and close invalid issues with a technical response.