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/mountainunicorn/add/dashboardnpx skills add MountainUnicorn/add --skill dashboardgit clone --depth 1 https://github.com/MountainUnicorn/addWrote 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/mountainunicorn/add/dashboard)<a href="https://agentmods.dev/skills/mountainunicorn/add/dashboard"><img src="https://agentmods.dev/badge/skills/mountainunicorn/add/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.00019 | $0.02966 |
| Opus 5 | $0.00010 | $0.01483 |
| Sonnet 5 | $0.00004 | $0.00593 |
| Haiku 4.5 | $0.00002 | $0.00297 |
Grade A, and why
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 4d 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADD Dashboard Command v{{VERSION}}
Generate a self-contained HTML dashboard at reports/dashboard.html by reading the project's .add/ directory, specs, docs, and config. The file opens in the browser and gives anyone — developer, PM, or founder — a real-time picture of the project's state.
Token economy: dashboard rendering is mechanical work. When sub-agent dispatch is available, delegate the bulk HTML generation to the fast tier per rules/model-roles.md; keep the frontier-model context for judgment — data selection, status interpretation, and final review.
Pre-Flight
- Read
.add/config.json— if not found, abort: "No ADD project found. Run /add:init first." - Check for session handoff — per the Session-Handoff Preflight in
${CLAUDE_PLUGIN_ROOT}/references/skill-epilogue.md.
Data Gathering
Read ALL of these source files. If a file doesn't exist, note it as missing and continue:
| Source | Path | Data |
|---|---|---|
| Config | .add/config.json |
Project name, maturity level, WIP limit, current cycle |
| PRD | docs/prd.md |
H2 headings = requirement sections, count total |
| Specs | specs/*.md |
Feature name (H1), Status (frontmatter), AC count (lines with AC- prefix or - [ ]/- [x] under Acceptance Criteria heading) |
| Milestones | docs/milestones/*.md |
Name, status, feature lists, completion dates |
| Cycles | .add/cycles/cycle-*.md |
Cycle number, status, features, validation result |
| Learnings | .add/learnings.json |
Entry count by category |
| Decisions | .add/decisions.md |
Decision count (H2 sections) |
| Changelog | CHANGELOG.md |
Version entries |
| Retro scores | .add/retro-scores.json |
Score trend data (collab, ADD effectiveness, swarm) |
| Retros | .add/retros/retro-*.md |
Dates and period summaries |
| Git log | git log --oneline |
Recent commits, tags for releases |
Spec Status Mapping
Map ADD spec frontmatter Status: to dashboard positions:
| Spec Status | Dashboard Label | Hill % |
|---|---|---|
| Draft | draft | 10% |
| Approved | specced | 25% |
| (has plan) | planned | 40% |
| Implementing | in-progress | 60% |
| Complete | done | 90% |
| Blocked | blocked | off-hill |
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.
- 4d ago First seen · 257 lines · 19 tokens per session scan A 38eaa518c068
dashboard is a skill published in the GitHub repository MountainUnicorn/add (11 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 2,966 once invoked, about $0.0001 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
flow-next-pilot
Single-tick autonomous build-loop conductor. One spec or the backlog, one stage per tick (pipeline.chainStages chains qa into make-pr), emits PILOTVERDICT. Use when asked to pilot a spec or backlog.
backlog
Read, work, and maintain a Git repo's deferred-work items in docs/backlog/, one file per item. Use when the user says "backlog", "check backlog", "what's on my backlog", "work the backlog", "address the backlog", "add to backlog", "clean up backlog", or when a review or task produced items that are real but not being…
backlog
EXPERIMENTAL. Use when working the project-wide out-of-scope backlog at paad/code-reviews/backlog.md — cleaning it of entries that are already fixed or gone, or picking the next entry and fixing it end-to-end. Not for producing backlog entries — that is /agentic-review — and not for reviewing a branch diff.
sync-project-docs
Usar para sincronizar la documentación viva del proyecto después de una fase. También: actualizar docs/project, índice, architecture.md, compliance.md, threat-model.
graduate-backlog
Graduate a project's in-repo backlog (roadmap phases, sprint deliverables, ADRs) onto a forge issue tracker at a thin-hybrid default, once the backlog outgrows a single contributor. Use when a team needs to see and claim work that currently lives only in docs/roadmap and docs/sprints, when a repo has a mature in-repo…
st-setup-project
Smalltalk (Pharo/Squeak) project boilerplate creator. Use when the user asks to create a new Pharo/Smalltalk project from scratch, when project structure is missing (no src/ directory or .project file), when the user wants to start a new Smalltalk development project, or when setting up BaselineOf, Core, and Tests…