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 instructions/sethgammon/citadel/agents-mdgit 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.00773 | $0.00773 |
| Opus 5 | $0.00387 | $0.00387 |
| Sonnet 5 | $0.00155 | $0.00155 |
| Haiku 4.5 | $0.00077 | $0.00077 |
Grade A, and why
Citadel AGENTS.md 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Harness
An agent orchestration system for Codex. This repo IS the harness.
What This Is
The harness is a collection of skills, agents, hooks, and state files that enable Codex to operate autonomously on any codebase. It provides:
- Intent routing (
/do) that dispatches tasks to the right tool - Campaign persistence across sessions
- Parallel agent coordination with discovery sharing
- Automated quality enforcement through lifecycle hooks
Key Conventions
- Skills live in
skills/. Each skill is a directoryskills/{name}/SKILL.md. - Agents live in
agents/. They spawn as sub-processes with their own context. - Hooks live in
hooks_src/. Installed per-project viascripts/install-hooks.js. - The
init-projecthook auto-scaffolds per-project state on session start:.planning/— campaign state, fleet sessions, intake, telemetry.citadel/scripts/— utility scripts (telemetry, coordination, compression).claude/agent-context/— rules injected into sub-agents
- Campaign state lives in
.planning/campaigns/(per-project). - Fleet session state lives in
.planning/fleet/(per-project). - Templates live in
.planning/_templates/(copied from plugin on init). - Configuration lives in
.claude/harness.json(generated by/do setup, per-project).
Testing
Always run tests after modifying hooks or skills. Five levels:
| Command | What it checks | When to run |
|---|---|---|
node scripts/test-all.js |
Hooks + skill structure (fast, no LLM) | After any change |
node hooks_src/smoke-test.js |
Hooks only | After hook changes |
node scripts/verify-hooks.js |
Hook install + runtime (synthetic payloads, no LLM) | After hook changes |
node scripts/integration-test.js |
Full Pre→tool→Post pipeline sequences (no LLM) | After hook changes |
node scripts/skill-lint.js |
All SKILL.md structure | After skill changes |
node scripts/skill-bench.js |
Scenario file validity | After adding benchmarks |
node scripts/skill-bench.js --execute |
Live scenario execution | Before shipping |
node scripts/skill-bench.js --execute --verify-hooks |
Live execution + confirms hooks fired | Before shipping |
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 · 70 lines · 773 tokens per session scan A 96a1dd6adbd0
Citadel AGENTS.md is an instructions file published in the GitHub repository SethGammon/Citadel (912 stars, last pushed 4d ago), licensed MIT. It adds 773 tokens to every session, about $0.0039 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 instructions, from other repositories
spacedock AGENTS.md
Instructions for spacedock-dev/spacedock, covering agent instructions, priorities, expected commands, releasing and project shape.
Wakeflow AGENTS.md
Instructions for GxFn/Wakeflow, covering wakeflow source repository instructions, scope and safety, source ownership, change discipline and verification.
spacedock CLAUDE.md
Instructions for spacedock-dev/spacedock, a project described as: Zero-dep agent workflows with structured approval gates and adversarial review.
Wakeflow CLAUDE.md
Instructions for GxFn/Wakeflow, covering wakeflow source repository instructions for claude code, scope and safety, source ownership, change discipline and verification.
agent-plugins-skills copilot-instructions.md
Instructions for richfrem/agent-plugins-skills, covering copilot instructions for agent-plugins-skills, 1. think before coding, 2. simplicity first, 3. surgical changes and 4. goal-driven execution.
ideate AGENTS.md
Instructions for paultyng/ideate, covering agents.md, build features as mcp tools first, ui second, when to add ui and pattern.