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/sethgammon/citadel/donpx skills add SethGammon/Citadel --skill dogit clone --depth 1 https://github.com/SethGammon/CitadelWrote 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/do)<a href="https://agentmods.dev/skills/sethgammon/citadel/do"><img src="https://agentmods.dev/badge/skills/sethgammon/citadel/do.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.00074 | $0.05966 |
| Opus 5 | $0.00037 | $0.02983 |
| Sonnet 5 | $0.00015 | $0.01193 |
| Haiku 4.5 | $0.00007 | $0.00597 |
Grade B, and why
do scanned grade B 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 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
- `always-ask` or `null` → show prompt: "These look independent — run in parallel? [1=yes 2=always 3=no]" How it starts
The opening of the file, as written. The whole thing — 315 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/do — Unified Intent Router
Orientation
Use /do when the user wants something done but doesn't know (or care) which tool handles it.
Don't use when: you know the destination — invoke /marshal, /archon, /fleet, or any skill directly.
Commands
| Command | Behavior |
|---|---|
/do [anything] |
Classify intent, route to cheapest capable path |
/do status |
Show full harness dashboard (/dashboard) |
/do next |
Run the decision-first operator console for the next useful harness action |
/do operator |
Show the operator console without executing repairs |
/do preview <request> |
Show exact resolution or generated candidates and their boundary without executing |
/do --route /skill -- <request> |
Use an explicit validated route without bypassing activation or safety boundaries |
/do continue |
Resolve and run the deterministic continuation action |
/do --list |
Show all skills grouped by category with trigger keywords |
/do setup |
First-run experience — configure the harness for this project |
Protocol
Classification runs top-to-bottom. Exact commands resolve first. Natural-language requests use keyword matches only as candidate evidence for semantic classification.
Step 0: Skill Registry Check (Cost: ~0 on hit | ~50 tokens on miss)
Compare installed skill directories with core/skills/routing-table.json. If they
match, continue without reading skill bodies. For each unknown skill, read only
its frontmatter and use name, description, and trigger_keywords as session-local Tier 2 match targets, then report:
"Discovered {N} new skill(s): {names}. Run /do setup to regenerate routing."
Do not write registration fields into harness.json; schema-v2 config is exact and generated routing is a projection, not config authority.
Tier 0: Exact Command Match (Cost: ~0 tokens | Latency: <1ms)
Normalize case, apostrophes, and whitespace, then compare the entire input. Never match a Tier 0 command because its word appears inside a larger request.
What ships with it
4 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.
- 4d ago First seen · 315 lines · 74 tokens per session scan B 8f85678d1423
do is a skill published in the GitHub repository SethGammon/Citadel (917 stars, last pushed 7d ago), licensed MIT. It adds 74 tokens to every session and 5,966 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
debrief
This skill should be used when the user asks to "debrief", "record what happened", "session summary", "write a debrief", or wants to capture session activity (commits, task state changes, decisions, issues) into a structured record for the next session.
refit
This skill should be used when the user asks to "refit a workflow", "upgrade a workflow", "update workflow scaffolding", or wants to bring an existing workflow's scaffolding files up to date with the current Spacedock version.
fo-dispatch-recovery
Claude dispatch failure recovery — Break-Glass Manual Dispatch (the manual Agent() template) and Context Budget Failure/Dead Ensign Handling (the budget-unavailable stderr conditions, the recovery clause, dead-ensign bookkeeping). Read ONLY at its resident triggers inside claude-fo-dispatch.md — a non-zero or…
fo-status-viewer
First-officer status query/mutate/display surface — the status command flag docs, --set field docs, canonical captain-facing invocations, the Captain-Facing State Display rendering, and the GitHub-issue-filing approval gate. Invoke at the first ad-hoc status question, --set mutation, --next-id/--resolve lookup, or…
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.
agent-workflow-playbook
AI Agent Workflow & Skill Architecture Guide — turn expert work into measurable, reusable agent systems. Covers workflow discovery, skill decomposition, harness design, evaluation, human escalation, observability, cost control, and multi-agent orchestration. Includes a measured marketing-delivery case: 15 people × 3–4…