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 BlackBeltTechnology/pi-agent-dashboard --skill node-inspect-debuggergit clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboardWrote 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/blackbelttechnology/pi-agent-dashboard/node-inspect-debugger)<a href="https://agentmods.dev/skills/blackbelttechnology/pi-agent-dashboard/node-inspect-debugger"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/node-inspect-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/blackbelttechnology/pi-agent-dashboard/node-inspect-debugger"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/node-inspect-debugger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 121 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00083 | $0.02386 |
| Opus 5.5 | $0.00033 | $0.00954 |
| Sonnet 5.5 | $0.00017 | $0.00477 |
| Haiku 4.5 | $0.00008 | $0.00239 |
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 7d 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:<port>/json/list # find the webSocketDebuggerUrl / port How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Node Inspect Debugger
Overview
console.log is a guess with a print statement attached — you have to already suspect where to look and what to print. A breakpoint inverts that: you stop the world at a line and read every local and closure variable in the frame, walk the call stack, and evaluate expressions in the paused context. When the bug lives in state a log can't cheaply reach — a closure captured three calls ago, a paused async frame, the Electron main process, the internals of a long-lived WebSocket server — the inspector is the tool.
This skill is the TOOL half of a pair; the METHOD is systematic-debugging (its Phase 1 "gather evidence" and Phase 3 "test one variable" are exactly when you reach for a breakpoint).
When to Use
Reach for the inspector when the state you need is expensive or impossible to log:
- The dashboard server (
packages/server, TypeScript run directly via the Node-native strip-only loader; the server has no jiti path) — request handlers whose failure depends on accumulated in-memory state. - The restart orchestrator / PTY workers (
restart-helper.ts) — a detached process whose closure state you can'tconsole.logfrom the parent. - Dual WebSocket server closure state — connection maps and buffers held in closures across the bridge and browser servers.
- The Electron main process — lifecycle/bootstrap state that never reaches a browser console.
- The bridge extension — code running inside every pi session, where adding logs means reloading every session.
If a single well-placed console.log would answer the question, use the log. The inspector earns its setup cost when the state is deep, closure-bound, or in a process you can't easily instrument.
Two tiers
| Tier | Use when | Interface |
|---|---|---|
REPL (node inspect) |
interactive, one-off, you're driving | the node inspect command REPL |
| Programmatic CDP | scripted, repeatable, or attaching from another process | scripts/cdp-inspect.ts (this skill) |
What ships with it
2 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.
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.
- 7d ago Changed · +1 lines ec3db8bda503
- 13d ago Changed · +20 lines b9d3b820fab7
- 1mo ago First seen · 136 lines · 83 tokens per session scan A 0843b53ab597
node-inspect-debugger is a skill published in the GitHub repository BlackBeltTechnology/pi-agent-dashboard (325 stars, last pushed today), licensed MIT. It adds 83 tokens to every session and 2,386 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
goga-prototype-plan-verification
Verification of the assembled architecture plan against the DSL.
goga-change-investigator
Evidence-driven root cause investigation.
goga-change-tracer
Semantic behavior reconstruction via tracing.
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…
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.