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/decision-mapnpx skills add SethGammon/Citadel --skill decision-mapgit 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/decision-map)<a href="https://agentmods.dev/skills/sethgammon/citadel/decision-map"><img src="https://agentmods.dev/badge/skills/sethgammon/citadel/decision-map.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.00077 | $0.01352 |
| Opus 5 | $0.00039 | $0.00676 |
| Sonnet 5 | $0.00015 | $0.00270 |
| Haiku 4.5 | $0.00008 | $0.00135 |
Grade A, and why
decision-map 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity
You are the planning-loop engine. You hold thinking state across sessions in one
compact, git-tracked artifact — lighter than a campaign, heavier than a TODO. You
sit below archon and fleet: use this for the figuring-out that precedes a
campaign, when work is still being discovered rather than executed. When a ticket
resolves into buildable work, it graduates into .planning/intake/ for autopilot.
Orientation
Use when:
- An idea has open questions that must be resolved before it can be built.
- The work is too fuzzy for a campaign and too large for a single intake item.
- Planning needs to survive across sessions without re-deriving context each time.
Don't use when:
- The work is already buildable — write a
.planning/intake/item directly. - The work is already scoped and sequenced — run a campaign (
archon/fleet).
Protocol
Critical constraints (do not violate)
- ONE MAP PER PLANNING EFFORT. A single Markdown file at
.planning/decision-maps/<slug>.md, git-tracked. It is the canonical artifact and is reloaded whole as context at the start of every session. - ONE TICKET PER SESSION. Resolve exactly one ticket, then stop. Map-building is its own session; do not bootstrap and resolve in the same run.
- FOG OF WAR. The map is deliberately incomplete past the frontier. Do not invent tickets you cannot yet see. Push the frontier forward by resolving, not speculating.
- BLOCKING EDGES ARE REQUIRED. Every ticket declares what blocks it. Never resolve a ticket whose blockers are open.
Ticket types
- Research — read docs, third-party APIs, or local resources (planning notes, knowledge base, source). Output: findings recorded in the ticket body.
- Prototype — throwaway code that answers a question (a small harness for logic/state, or alternate UIs for look-and-feel). Keep only the answer, not the code.
- Grilling — a conversation that sharpens a decision. Runs the
grilldiscipline.
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 · 131 lines · 77 tokens per session scan A 3dcd6821c399
decision-map is a skill published in the GitHub repository SethGammon/Citadel (916 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 1,352 once invoked, about $0.0004 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
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.
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…
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".
ast-grep
Run code analysis and refactoring with ast-grep. Use when doing AST-based modifications, structural search, linting across code shape, or replacing regex-fragile transformations.