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 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/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/decision-map"><img src="https://agentmods.dev/badge/skills/sethgammon/citadel/decision-map.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00077 | $0.01352 |
| Opus 5.5 | $0.00031 | $0.00541 |
| Sonnet 5.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 1mo 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.
- 1mo ago First seen · 131 lines · 77 tokens per session scan A 3dcd6821c399
decision-map is a skill published in the GitHub repository SethGammon/Citadel (924 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 1,352 once invoked, about $0.0003 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
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…
drift-detect
Use when the user says "plan drift", asks whether the roadmap, plans, or docs still match the code, or is deciding what to rebuild when restarting a stalled project. For doc-vs-code drift inside a specific diff, use sync-docs.
github-backlog-triage
Use when the user invokes backlog triage for a GitHub repo's open issues and PRs. Not for proactive triage, non-GitHub trackers, or single bug issues: use github-bug-report-triage.
setup-repo-skills
Use when the user wants one-time repository setup for tracker, triage labels, and domain conventions. Not for ongoing triage, issue creation, or multi-repo setup.
git-history-analysis
Use when the user asks about recent engineering work, what the team is working on, planning or roadmap material, or an explicitly requested Slack summary. Not for remote or irreversible changes.
gitlab-ops
Use this skill when performing VCS operations on GitLab or GitHub repositories — creating, updating, or closing issues and MRs, applying label taxonomy, running glab/gh CLI commands, or resolving project paths dynamically. Acts as the single source of truth for CLI command syntax and label conventions; consuming…