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 rules/danielvm-git/bigpowers/visual-dashboardgit clone --depth 1 https://github.com/danielvm-git/bigpowersWrote 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/rules/danielvm-git/bigpowers/visual-dashboard)<a href="https://agentmods.dev/rules/danielvm-git/bigpowers/visual-dashboard"><img src="https://agentmods.dev/badge/rules/danielvm-git/bigpowers/visual-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 | $0.00049 | $0.00481 |
| Opus 5 | $0.00024 | $0.00241 |
| Sonnet 5 | $0.00010 | $0.00096 |
| Haiku 4.5 | $0.00005 | $0.00048 |
Grade A, and why
visual-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 today.
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/api/status?projectDir=$PWD" | jq .release.version What it actually says
Visual Dashboard
HARD GATE — HARD GATE — Dashboards are read-only. Do NOT use visualization to make decisions without consulting the source data. 'The chart looks better' is not a decision.
Browser-based visual companion for bigpowers. Visualizes architecture, plans, and status.
HTTP cockpit (YAML SoT)
Start the server:
bash visual-dashboard/scripts/start-server.sh
Endpoints:
| Route | Purpose |
|---|---|
GET /api/status?projectDir=<abs> |
JSON: state, release, epics[], planning_status, active_epic |
GET /cockpit.html?projectDir=<abs> |
Read-only PM view (planning left, epics right) |
GET / |
Agent-pushed HTML screens (legacy, unchanged) |
Example:
curl -s "http://127.0.0.1:PORT/api/status?projectDir=$PWD" | jq .release.version
Implementation: visual-dashboard/scripts/read-specs-status.cjs + server.cjs.
Opencode Progress Panel
Projects using bigpowers in opencode can read specs/state.yaml, specs/release-plan.yaml, and active specs/epics/*.yaml directly (no checkbox ### WS1 markdown).
Required YAML keys:
- state.yaml —
active_flow,active_epic_id,git,handoff,epic_cycle - release-plan.yaml —
release.version,epics[]withid,title,wsjf,file - execution-status.yaml —
development_statusmap (story/epic →done|pending) - planning-status.yaml — discover workflows and
status: done|pending
Agent screens (optional)
Push HTML to the dashboard session dir for rich diagrams. See start-server.sh for CONTENT_DIR.
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.
- today First seen · 50 lines · 49 tokens per session scan A 398f50f75c51
visual-dashboard is a cursor rule published in the GitHub repository danielvm-git/bigpowers (163 stars, last pushed 2d ago), licensed MIT. It adds 49 tokens to every session and 481 once invoked, about $0.0002 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
app-router-patterns
Next.js 14+ App Router patterns — Server Components, Client Components, Route Handlers, Server Actions, and metadata API.
00-project-rules
ContextOS core project rules and role orchestration.
context-os
ContextOS rules for context-os.
database
Database architecture, schema design, Prisma, Drizzle ORM, indexing strategies, migrations, and N+1 query resolution.
vue
Rules for Vue (2 and 3) single-file components.