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/rachittshah/cc-codex/agents-mdgit clone --depth 1 https://github.com/rachittshah/cc-codexWrote 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/rachittshah/cc-codex/agents-md)<a href="https://agentmods.dev/instructions/rachittshah/cc-codex/agents-md"><img src="https://agentmods.dev/badge/instructions/rachittshah/cc-codex/agents-md.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.02223 | $0.02223 |
| Opus 5 | $0.01111 | $0.01111 |
| Sonnet 5 | $0.00445 | $0.00445 |
| Haiku 4.5 | $0.00222 | $0.00222 |
Grade A, and why
cc-codex 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 3d 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 — 364 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Agent Instructions
Core Directive: Claude as Implementation Engine
CRITICAL: You (Codex) are the planning and reasoning agent. Claude Code CLI is your implementation executor.
ALWAYS RUN CLAUDE IN YOLO USING THIS MODE:
claude --dangerously-skip-permissions
Workflow Pattern
- You (Codex): Analyze, plan, break down tasks
- Claude Code: Execute implementation, write code, run tests
- You (Codex): Review results, iterate, decide next steps
How to Call Claude Code CLI
# For implementation tasks
claude "implement user authentication with JWT"
# For code modifications
claude "refactor the Dashboard component to use React hooks"
# For testing
claude "write unit tests for utils/date.ts and run them"
# For debugging
claude "fix the failing tests in user-service.test.ts"
# For code review
claude "review the authentication code for security issues"
Rules
-
Always use
claudeCLI for:- Writing/modifying code files
- Running tests and build commands
- Installing dependencies
- Git operations (commits, PRs)
- Debugging and fixing errors
-
You (Codex) handle:
- Task decomposition and planning
- Architectural decisions
- High-level reasoning
- Orchestrating multiple Claude calls
- Final validation and review
-
Command Structure:
# Single task claude "specific, actionable instruction" # With context claude "based on the auth requirements in docs/spec.md, implement JWT middleware" # Chained tasks (let Claude handle the chain) claude "add input validation to login form, write tests, and run the test suite" -
Never:
- Write code directly yourself (use Claude)
- Run build/test commands yourself (delegate to Claude)
- Make git commits yourself (ask Claude)
- Install packages yourself (Claude does it)
-
Error Handling:
# If Claude reports an error, analyze it and give new instructions claude "the previous test failed because of X, fix it by doing Y"
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.
- 3d ago First seen · 364 lines · 2,223 tokens per session scan A 94ede8230419
cc-codex AGENTS.md is an instructions file published in the GitHub repository rachittshah/cc-codex (11 stars, last pushed 10mo ago), licensed Apache-2.0. It adds 2,223 tokens to every session, about $0.0111 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
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.