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/SethGammon/Citadelnpx agentmods add skills/sethgammon/citadel/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/sethgammon/citadel/dashboard)<a href="https://agentmods.dev/skills/sethgammon/citadel/dashboard"><img src="https://agentmods.dev/badge/skills/sethgammon/citadel/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/sethgammon/citadel/dashboard"><img src="https://agentmods.dev/badge/skills/sethgammon/citadel/dashboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 Agent Snooping · line 281 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 284 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00054 | $0.03636 |
| Opus 5.5 | $0.00022 | $0.01454 |
| Sonnet 5.5 | $0.00011 | $0.00727 |
| Haiku 4.5 | $0.00005 | $0.00364 |
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 28d 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 — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dashboard — Harness Observability Dashboard
When to Use
- "What's happening?" / "Status?" / "What's going on?"
- "Show activity" / "Show me the dashboard"
- After returning to a project after time away
- When /do routes "status", "dashboard", "what's happening", "what's going on", "show activity"
- Directly:
/dashboard
Inputs
None required. Works with whatever state exists on disk.
Protocol
Step 0: RUN DASHBOARD IMPLEMENTATION
Run the local dashboard implementation from the project root:
node scripts/dashboard.js
If the package scripts are available, this equivalent command is also valid:
npm run dashboard
The script is read-only. It renders a user-facing control-plane snapshot from
.planning/, telemetry, hook config, coordination state, worktrees, and cost
data. Use the manual collection protocol below only as a fallback if the script
is missing or fails in the current project.
Step 1: COLLECT STATE
Read the following sources. Each is optional — if a file or directory doesn't exist, treat it as empty. Never crash on missing state.
Campaigns:
- Glob
.planning/campaigns/*.md - For each file, read the first 40 lines to extract:
Status:fieldDirection:field (truncate to 60 chars)- Phase progress (search for
Phase N of Mor## Phaseheadings) - Most recent line starting with
- [from the Decision Log
- If all phases are complete but status is still active, report
needs-completionand show:node scripts/campaign.js complete <slug> --archive - If a campaign is marked completed but still lives in
.planning/campaigns/, reportneeds-archiveand show the same archive command. - If prior build/verify phases are complete but the
review-packageExit Evidence row is still pending, missing, or points at a missing local package, report a repair before campaign completion:node scripts/package-delivery.js <slug>
Cost Data (two sources, prefer real):
- Primary: run
node scripts/session-tokens.js --todayand--all— reads Claude Code's native session JSONL for exact token counts - Fallback: read
.planning/telemetry/session-costs.jsonl; cost priorityreal_cost>override_cost>estimated_cost; group bycampaign_slug, sum cost/agents/minutes, compute grand total - Live session: read
.planning/telemetry/cost-tracker-state.jsonfor burn rate - Label real data "(real)" and estimates "(est)"
What ships with it
3 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.
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.
- 28d ago Changed 41ca396e0542
- 1mo ago First seen · 308 lines · 54 tokens per session scan A defd4eee5736
dashboard is a skill published in the GitHub repository SethGammon/Citadel (925 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 3,636 once invoked, about $0.0002 per session on Opus 5.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
compose-org
Run a task as an evolved multi-agent ORG using the installed liquid-org framework — where YOU (the running Claude) embody the org: you ask liquid-org which proven team topology + specialist personas to use (retrieved from its evolved pool, or assembled fresh), then dispatch ONE SUBAGENT PER TALENT to play each role…
liquid-rank
Rank the available skills by RELEVANCE to the current task, on demand, using liquid-org's read-only hermes skill ranker. This is an EXPLICIT, OPT-IN selector you invoke WHEN you want help choosing the most relevant skill for what you're doing — it is NOT default, automatic skill selection, and it does NOT decide for…
present-gate
First-officer gate-presentation rendering — the captain-facing gate-review template and assembly rules, including workflow-owned finding labels. Invoke at the gate point after the FO has decided a stage must be presented.
audit-project
Run an iterative multi-agent code audit until critical and high findings are resolved. Use when the user says "audit my code", "find all the bugs", "deep code audit", "iterative review", or "review until clean".
prototype
Use when asked to prototype one design question through a cheap logic or UI experiment, including button-driven state-model checks. Not for polished artifacts: use polished-web-prototype.
contexts
Use when the user says "get context on X", "how does X work", or wants architectural orientation before coding.