Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add SienkLogic/plan-build-run/plugin install pbrWrote 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/sienklogic/plan-build-run/dashboard)<a href="https://agentmods.dev/skills/sienklogic/plan-build-run/dashboard"><img src="https://agentmods.dev/badge/skills/sienklogic/plan-build-run/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.00013 | $0.00485 |
| Opus 5 | $0.00006 | $0.00243 |
| Sonnet 5 | $0.00003 | $0.00097 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
dashboard 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -o /dev/null -w "%{http_code}" http://localhost:<port>/ What it actually says
STOP — DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by Claude Code's plugin system. Begin executing immediately.
Step 0 — Immediate Output
Before ANY tool calls, display this banner:
╔══════════════════════════════════════════════════════════════╗
║ PLAN-BUILD-RUN ► DASHBOARD ║
╚══════════════════════════════════════════════════════════════╝
Then proceed to Step 1.
Behavior
-
Parse arguments: Extract
--port Nfrom the user's input. Default to3141. -
Locate dashboard: The dashboard lives at the repository root
dashboard/directory (NOT under${CLAUDE_PLUGIN_ROOT}). Resolve the repo root from<cwd>— for PBR's own repo this is the project root; for installed plugins, usegit rev-parse --show-toplevelor walk up from${CLAUDE_PLUGIN_ROOT}to finddashboard/. -
Check dependencies: Check if
<repo-root>/dashboard/server/node_modules/exists. If not, run:npm run dashboard:install --prefix <repo-root> -
Launch dashboard: Run in background via Bash:
node <repo-root>/dashboard/bin/cli.cjs --dir <cwd> --port <port> &Use
&to background the process so it doesn't block the session. -
Verify startup: After launching, check the process is responding:
curl -s -o /dev/null -w "%{http_code}" http://localhost:<port>/ -
Output to user:
Dashboard running at http://localhost:<port> Open this URL in your browser to view your project's planning state.
Notes
- If the port is already in use, the dashboard will fail to start — suggest the user try a different port with
--port. - The dashboard watches
.planning/for live updates via WebSockets.
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 · 59 lines · 13 tokens per session scan A 83b9d459e59e
dashboard is a skill published in the GitHub repository SienkLogic/plan-build-run (17 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 485 once invoked, about $0.0001 per session on Opus 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-09-03.
Other skills, from other repositories
moai-workflow-spec
SPEC workflow orchestration with EARS format requirements, acceptance criteria, and Plan-Run-Sync integration for MoAI-ADK development. Use when creating SPEC documents or defining acceptance criteria.
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
moai-workflow-templates
Template management system for code boilerplates, feedback templates, scaffolding, and project optimization workflows. Use when creating templates, generating boilerplate files, or managing scaffolding.
moai-workflow-project
Integrated project management system covering documentation, language initialization, template optimization, docs generation, and JIT document loading. Absorbed from moai-workflow-templates, moai-docs-generation, and moai-workflow-jit-docs.
moai
MoAI unified orchestrator for autonomous development. Routes natural language or subcommands (plan, run, sync, project, fix, loop, mx, feedback, review, clean, codemaps, gate, e2e, harness, goal, todo) to specialized agents.