Borrowing it
Nothing to install: this file belongs to SethGammon/Citadel. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SethGammon/Citadel/main/AGENTS.mdgit 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/instructions/sethgammon/citadel/agents-md)<a href="https://agentmods.dev/instructions/sethgammon/citadel/agents-md"><img src="https://agentmods.dev/badge/instructions/sethgammon/citadel/agents-md/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/instructions/sethgammon/citadel/agents-md"><img src="https://agentmods.dev/badge/instructions/sethgammon/citadel/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00827 | $0.00827 |
| Opus 5.5 | $0.00331 | $0.00331 |
| Sonnet 5.5 | $0.00165 | $0.00165 |
| Haiku 4.5 | $0.00083 | $0.00083 |
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 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 — 72 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.
- 1mo ago Changed · +2 lines · +54 tokens per session 51453b103436
- 1mo ago 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 (923 stars, last pushed today), licensed MIT. It adds 827 tokens to every session, about $0.0033 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).