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 skills add SethGammon/Citadel --skill fleetgit 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/fleet)<a href="https://agentmods.dev/skills/sethgammon/citadel/fleet"><img src="https://agentmods.dev/badge/skills/sethgammon/citadel/fleet/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/fleet"><img src="https://agentmods.dev/badge/skills/sethgammon/citadel/fleet.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Data Exfiltration · line 53 Code or instructions that leak agent conversation context to external services, potentially exposing sensitive user interactions.Fix: Remove any code that sends prompts, responses, or session data externally. Preserve user privacy; never exfiltrate conversation content.
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.00056 | $0.05773 |
| Opus 5.5 | $0.00022 | $0.02309 |
| Sonnet 5.5 | $0.00011 | $0.01155 |
| Haiku 4.5 | $0.00006 | $0.00577 |
Grade A, and why
fleet 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 9d 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 — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fleet — Parallel Coordinator
Use for 3+ independent work streams that can run simultaneously in isolated worktrees. Do NOT use for single-file scope, linear work, or when a marshal or skill suffices.
Orientation
Use when: Running 2+ independent work streams in parallel — tasks with non-overlapping file scopes that can execute simultaneously.
Don't use when: Work must execute sequentially or accumulate findings across phases (use /archon), a single orchestrated session is enough (use /marshal), or the task is simple enough for a bare skill.
Commands
| Command | Behavior |
|---|---|
/fleet [direction] |
Decompose direction into parallel streams, execute in waves |
/fleet [path-to-spec] |
Read a spec file, decompose into streams |
/fleet continue |
Resume from the last fleet session file |
/fleet (no args) |
Health diagnostic → work queue → execute |
/fleet --quick [task1]; [task2] |
Lightweight parallel mode for solo devs — 2+ tasks, single wave, governed merge, minimal durable receipt |
/fleet --speculative N [direction] |
Try N different approaches to the same task in parallel — see Speculative Mode below |
/fleet --teams [direction] |
Pilot: native task spine when CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS is set, see Teams Mode (experimental) below |
Protocol
Step 1: WAKE UP
- Read AGENTS.md, then CLAUDE.md if present (project conventions)
- Check
.planning/campaigns/for active campaigns - Check
.planning/coordination/claims/for external claims - Determine input mode: directed, spec-driven, continuing, or undirected
- Load prior session context: if
.planning/momentum.jsonexists, runnode .citadel/scripts/momentum-read.cjsand use the active scopes and recurring decisions to inform work queue prioritization. Skip silently if the file is absent or output is empty.
Wave context restoration: Use the Claude Code Compaction API to restore fleet session context. Do NOT read
.claude/compact-state.json— deprecated in favour of server-side compaction (available on Opus 4.6+). Fleet session files (.planning/fleet/session-{slug}.md) remain the source of truth for inter-wave discovery relay; compaction handles agent memory, not campaign state. If the Compaction API is unavailable, read the fleet session file's Continuation State directly.
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.
- 9d ago Changed f73abe0a6ab8
- 21d ago Changed · +3 lines 8a794bd2524f
- 26d ago Changed b0deb6fd18a4
- 1mo ago Changed 17b897454d86
- 1mo ago First seen · 310 lines · 56 tokens per session scan A c28c50d885c7
fleet is a skill published in the GitHub repository SethGammon/Citadel (924 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 5,773 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.