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/blackbelttechnology/pi-agent-dashboard/debug-dashboardnpx skills add BlackBeltTechnology/pi-agent-dashboard --skill debug-dashboardgit 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/debug-dashboard)<a href="https://agentmods.dev/skills/blackbelttechnology/pi-agent-dashboard/debug-dashboard"><img src="https://agentmods.dev/badge/skills/blackbelttechnology/pi-agent-dashboard/debug-dashboard.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.00089 | $0.01650 |
| Opus 5 | $0.00044 | $0.00825 |
| Sonnet 5 | $0.00018 | $0.00330 |
| Haiku 4.5 | $0.00009 | $0.00165 |
Grade A, and why
debug-dashboard 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 6d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Dashboard
System-level debugging for the running pi-agent-dashboard. Three layers:
┌─────────────────────────────────────────────────────────┐
│ Layer 1 — Is the server alive? │
│ npx tsx ./scripts/health-probe.ts │
│ npx tsx ./scripts/tail-server-log.ts │
└─────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────┐
│ Layer 2 — Are the bridges connecting? │
│ npx tsx ./scripts/list-sessions.ts │
│ npx tsx ./scripts/tail-server-log.ts --errors│
└─────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────┐
│ Layer 3 — Is the UI rendering? │
│ (use the browser skill) │
└─────────────────────────────────────────────────────────┘
First moves — always run these
npx tsx ./scripts/health-probe.ts # mode + uptime + version, or "not-running"
npx tsx ./scripts/tail-server-log.ts # last 50 lines of current run
npx tsx ./scripts/list-sessions.ts # connected pi sessions via REST
Scripts are TypeScript (cross-platform). All invocations use
npx tsxso they work on Linux, macOS, and Windows.tsxis already a project dep.
If health-probe says "not-running" → server isn't up. Check server.log for the most recent start banner ([bootstrap] ready ...) and what came after. The log appends with timestamped headers per start, so the last banner block is the relevant one.
When the server is up but misbehaving
| Symptom | Likely cause | Where to look |
|---|---|---|
| Restart loops | Stale port held by zombie, or restart racing with bridge auto-start |
lsof -i :8000, then pi-dashboard stop (kills by port, not just PID) |
EADDRINUSE on start |
Concurrent spawn from multiple pi sessions | Harmless — losing process exits silently. Check log. |
| Bridge connects then disconnects | server_restarting broadcast active, or version skew |
grep server_restarting in server.log; check /api/health for version |
| Blank page in browser | Vite not running in dev mode (silent fallback to prod build); or auth blocking | Check /api/health.mode; check auth settings |
New session won't start / yellow spawn_register_timeout, no card |
pi crashed at startup (bad extension) OR host overload |
See references/known-issues.md → "New session won't start" — manual pi --mode rpc run splits crash vs overload |
Cannot connect to dashboard server on Electron boot |
launchDashboardServer fell back to process.execPath (Electron GUI binary) |
See references/known-issues.md → "Electron Node bin selection" |
| Fastify crashes immediately | Bad Node version (22.0–22.17.x or 24.1–24.2.x per nodejs/node#58515) | node --version — must be ≥ 22.18.0 |
What ships with it
18 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.
- references/isolated-verification.md 6.0 KB
- references/known-issues.md 8.0 KB
- references/known-issues.md.AGENTS.md 415 B
- references/log-locations.md 3.9 KB
- references/log-locations.md.AGENTS.md 424 B
- references/test-failure-triage.md 4.5 KB
- references/test-failure-triage.md.AGENTS.md 388 B
- references/ui-debug.md 1.9 KB
- references/ui-debug.md.AGENTS.md 402 B
- scripts/health-probe.ts 3.5 KB runs code
- scripts/health-probe.ts.AGENTS.md 324 B
- scripts/list-sessions.ts 2.6 KB runs code
- scripts/list-sessions.ts.AGENTS.md 328 B
- scripts/run-tests-triage.ts 3.0 KB runs code
- scripts/run-tests-triage.ts.AGENTS.md 458 B
- scripts/tail-server-log.ts 2.6 KB runs code
- scripts/tail-server-log.ts.AGENTS.md 373 B
- SKILL.md.AGENTS.md 380 B
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.
- 6d ago First seen · 115 lines · 89 tokens per session scan A be1a45192006
debug-dashboard is a skill published in the GitHub repository BlackBeltTechnology/pi-agent-dashboard (274 stars, last pushed today), licensed MIT. It adds 89 tokens to every session and 1,650 once invoked, about $0.0004 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-30.
Other skills, from other repositories
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…
goga-change-investigator
Evidence-driven root cause investigation.
goga-change-tracer
Semantic behavior reconstruction via tracing.
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.
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.