Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/nobodyohm-web/Thotnpx agentmods add skills/nobodyohm-web/thot/node-inspect-debuggerWrote 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/nobodyohm-web/thot/node-inspect-debugger)<a href="https://agentmods.dev/skills/nobodyohm-web/thot/node-inspect-debugger"><img src="https://agentmods.dev/badge/skills/nobodyohm-web/thot/node-inspect-debugger.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.00019 | $0.02954 |
| Opus 5 | $0.00010 | $0.01477 |
| Sonnet 5 | $0.00004 | $0.00591 |
| Haiku 4.5 | $0.00002 | $0.00295 |
Grade A, and why
node-inspect-debugger scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://127.0.0.1:9229/json/list | jq -r '.[0].webSocketDebuggerUrl' This is a copy
100% identical to node-inspect-debugger — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Node.js Inspect Debugger
Overview
When console.log isn't enough, drive Node's built-in V8 inspector programmatically from the terminal. You get real breakpoints, step in/over/out, call-stack walking, local/closure scope dumps, and arbitrary expression evaluation in the paused frame.
Two tools, pick one:
node inspect— built-in, zero install, CLI REPL. Best for quick poking.ndb/ CDP viachrome-remote-interface— scriptable from Node/Python; best when you want to automate many breakpoints, collect state across runs, or debug non-interactively from an agent loop.
Prefer node inspect first. It's always available and the REPL is fast.
When to Use
- A Node test fails and you need to see intermediate state
- ui-tui crashes or behaves wrong and you want to inspect React/Ink state pre-render
- tui_gateway child processes (
_SlashWorker, PTY bridge workers) misbehave - You need to inspect a value in a closure that
console.logcan't reach without patching - Perf: attach to a running process to capture a CPU profile or heap snapshot
Don't use for: things console.log solves in under a minute. Breakpoint-driven debugging is heavier; use it when the payoff is real.
Quick Reference: node inspect REPL
Launch paused on first line:
node inspect path/to/script.js
# or with tsx
node --inspect-brk $(which tsx) path/to/script.ts
The debug> prompt accepts:
| Command | Action |
|---|---|
c or cont |
continue |
n or next |
step over |
s or step |
step into |
o or out |
step out |
pause |
pause running code |
sb('file.js', 42) |
set breakpoint at file.js line 42 |
sb(42) |
set breakpoint at line 42 of current file |
sb('functionName') |
break when function is called |
cb('file.js', 42) |
clear breakpoint |
breakpoints |
list all breakpoints |
bt |
backtrace (call stack) |
list(5) |
show 5 lines of source around current position |
watch('expr') |
evaluate expr on every pause |
watchers |
show watched expressions |
repl |
drop into REPL in current scope (Ctrl+C to exit REPL) |
exec expr |
evaluate expression once |
restart |
restart script |
kill |
kill the script |
.exit |
quit debugger |
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.
- 3d ago First seen · 320 lines · 19 tokens per session scan A bc89942b7638
node-inspect-debugger is a skill published in the GitHub repository nobodyohm-web/Thot (0 stars, last pushed 12d ago), licensed MIT. It adds 19 tokens to every session and 2,954 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to node-inspect-debugger, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
copilotkit-debug
Use when diagnosing CopilotKit issues -- runtime connectivity failures, agent not responding, streaming errors, tool execution problems, transcription failures, version mismatches, and AG-UI event tracing.
agent-merge-conflict-arbiter
Neutral arbiter for merge conflicts between two agents.
triage-issues
Triage GitHub issues in the googleapis/mcp-toolbox repo: propose the correct labels (type / priority / product / status), check for duplicates, verify a bug has enough info to act on, and draft a triage comment. Use whenever a maintainer asks you to triage, label, categorize, prioritize, or "look at" an issue (or a…
python-debugpy
Debug Python: pdb REPL + debugpy remote (DAP).
sglang-diffusion-benchmark-profile
Use when benchmarking denoise latency or profiling a diffusion bottleneck in SGLang.
trulens-diagnosis
Diagnose low evaluation scores and generate actionable improvement recommendations.