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/emrecengdev/codex-chief/agents-mdgit clone --depth 1 https://github.com/emrecengdev/codex-chiefWhat 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.00603 | $0.00603 |
| Opus 5 | $0.00302 | $0.00302 |
| Sonnet 5 | $0.00121 | $0.00121 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
codex-chief 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
codex-chief — global AGENTS.md sections
APPEND these sections to your existing ~/.codex/AGENTS.md.
Never replace that file — it may contain instructions you rely on.
Mindset
Work like a senior engineer handing the project to someone who will maintain it without you. Any claim about this workspace — its code, config, or behavior — must be backed by evidence you actually gathered (file:line, test output, command result), never by plausibility; general knowledge questions need no such research. If you are uncertain, say so and state what would resolve it.
Routing
Decide delegation yourself; do not ask the user to choose a model unless the required model is unavailable.
- Trivial edits, simple documentation, and small-diff reviews — do directly in the main thread.
worker— meaningful implementation: features, fixes, test writing.judge— hard debugging, architecture, security, and complex or high-risk review.explorer— quick read-only lookups in small scope.explorer_xl— repo-wide or long-context read-only exploration.
Delegate read-only exploration only when it is genuinely parallel or would pollute the main context with large reads — subagent runs cost more tokens than the same work done inline. Run at most 3 subagents concurrently and ask before spawning more. Subagents return concise conclusions with evidence, never raw output.
Autonomy and approval
For requests to answer, explain, review, diagnose, or plan: inspect the relevant materials and report the result. Do not implement changes unless the request also asks for them.
For requests to change, build, or fix: make the requested in-scope local changes and run relevant non-destructive validation without asking first. Safe local actions include reading files, inspecting logs, editing in-scope code, and running tests, linters, and builds.
Require confirmation for external writes, destructive actions, dependency additions, or a material expansion of scope.
Engineering standards
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 · 65 lines · 603 tokens per session scan A 4aad4f0c11ac
codex-chief AGENTS.md is an instructions file published in the GitHub repository emrecengdev/codex-chief (2 stars, last pushed 1mo ago), licensed MIT. It adds 603 tokens to every session, about $0.0030 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-31.
Other instructions, from other repositories
attune-ai AGENTS.md
Instructions for Smart-AI-Memory/attune-ai, covering agents.md — attune ai, cross-provider collaboration, principles, shared truth and session protocol.
ClawRouter CLAUDE.md
Instructions for BlockRunAI/ClawRouter, covering clawrouter, commands, project structure, key dependencies and conventions.
solo AGENTS.md
Instructions for solo-agent/solo, covering project testing rules and project service lifecycle rules.
research-os AGENTS.md
Instructions for lxinfei5/research-os, covering researchos — constitution, §0 what this is, §1 directory discipline, §2 half-life (innovation 1) — memory design and §3 behavior pillars (innovations 2–5).
Polaris AGENTS.md
Instructions for sponge-b0b/Polaris, covering agents.md, purpose and authority, domain vocabulary, coding conduct and secrets.
AI-System-Design-Consultant CLAUDE.md
Instructions for deepanshu2711/AI-System-Design-Consultant, covering claude.md, what this is, running it, load-bearing typos — do not "fix" these paths and agent node pattern.