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/danielvm-git/bigpowersnpx agentmods add skills/danielvm-git/bigpowers/visual-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/danielvm-git/bigpowers/visual-dashboard)<a href="https://agentmods.dev/skills/danielvm-git/bigpowers/visual-dashboard"><img src="https://agentmods.dev/badge/skills/danielvm-git/bigpowers/visual-dashboard/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/danielvm-git/bigpowers/visual-dashboard"><img src="https://agentmods.dev/badge/skills/danielvm-git/bigpowers/visual-dashboard.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 Excessive Agency · line 3 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00052 | $0.00486 |
| Opus 5.5 | $0.00021 | $0.00194 |
| Sonnet 5.5 | $0.00010 | $0.00097 |
| Haiku 4.5 | $0.00005 | $0.00049 |
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 1mo 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/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.
- 1mo ago First seen · 51 lines · 52 tokens per session scan A 648ee232da2c
visual-dashboard is a skill published in the GitHub repository danielvm-git/bigpowers (275 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 486 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
huashu-keynote-black
OpenDesign's all-hands: the year in review, the three priorities, and what every team owns next quarter. Built as a decision-grade corporate strategy deck for whole company.
ponytail-debt
Harvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.
kanban-board
A Kanban board is a visual task list with columns for stages such as To do, In progress, In review, and Done. It can show filters, labels, due dates, assignees, comments, and swimlanes that group cards.
ui-designer/component-specification
A specification for reusable interface components such as buttons, inputs, and cards. It defines their variations, sizes, and states, including hover, focus, disabled, loading, and error states.
pm/user-research
A user research guide for describing target users and mapping the steps, thoughts, feelings, and problems they experience while completing a task.
ui-designer/design-variants
A UI design method that creates two or three meaningfully different interface options, then compares their advantages and disadvantages.