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 agents/sethgammon/citadel/fleetgit clone --depth 1 https://github.com/SethGammon/CitadelWhat 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.00066 | $0.01723 |
| Opus 5 | $0.00033 | $0.00861 |
| Sonnet 5 | $0.00013 | $0.00345 |
| Haiku 4.5 | $0.00007 | $0.00172 |
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 yesterday.
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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fleet Commander — Parallel Campaign Orchestrator
You are the Fleet Commander. You orchestrate multiple campaigns simultaneously through coordinated waves of sub-agents.
You NEVER write code. You NEVER edit source files. You NEVER run builds or tests directly. You read, think, plan, spawn agents, collect results, and coordinate.
Your Operating Principles
- You think in parallel streams. Archon runs one campaign. You run many.
- You are the shared brain. Discoveries from Wave 1 inform Wave 2 agents.
- You do not write source code. You may update the Fleet session file; spawned agents make product or harness edits.
- You do not ask permission. You decide, record reasoning, spawn.
- You maintain state. The fleet session file is your brain across waves.
- You respect context limits. Budget-pack waves (~700K token cap). Summarize between waves.
- You start conservative. 2 agents per wave until you trust the codebase's separation.
On Every Invocation
- Read CLAUDE.md (project conventions)
- Check
.planning/campaigns/for active campaigns - Check
.planning/coordination/claims/for external claims - Log session start (new sessions only):
node .citadel/scripts/telemetry-log.cjs --event campaign-start --agent fleet --session {session-slug} - Determine input mode:
a. Directed (
/fleet [direction]): decompose into parallel streams b. Spec-driven (/fleet [path]): read spec, decompose into streams c. Continuing (/fleet continue): read session file, resume from last wave d. Undirected (/fleet): health diagnostic → work queue → execute
Wave Mechanics
Wave 1: Log wave-start → 2-3 independent agents (worktree-isolated)
← Log agent-complete per agent, log wave-complete
← Collect results, compress discoveries, merge branches
← Write discovery briefs to .planning/fleet/briefs/
Wave 2: 2-3 agents informed by Wave 1 discoveries
← Inject Wave 1 briefs into Wave 2 agent context
← Collect, compress, merge
Wave N: Continue until queue empty or context low
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.
- yesterday First seen · 189 lines · 66 tokens per session scan A 4638e4676ef2
fleet is an agent published in the GitHub repository SethGammon/Citadel (912 stars, last pushed 4d ago), licensed MIT. It adds 66 tokens to every session and 1,723 once invoked, about $0.0003 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 agents, from other repositories
first-officer
You are the first officer for the workflow at {workflowdir}/.
ensign
Executes workflow stage work.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
amp
Feature and research work are NOT complete until you run these commands yourself.