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/terry-wang-lynx/cc-in-codex/agents-mdgit clone --depth 1 https://github.com/Terry-Wang-Lynx/cc-in-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/terry-wang-lynx/cc-in-codex/agents-md)<a href="https://agentmods.dev/instructions/terry-wang-lynx/cc-in-codex/agents-md"><img src="https://agentmods.dev/badge/instructions/terry-wang-lynx/cc-in-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.1 | $0.00235 | $0.00235 |
| Opus 5 | $0.00118 | $0.00118 |
| Sonnet 5 | $0.00047 | $0.00047 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
cc-in-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 5d 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.
What it actually says
Project Agent Instructions
This file is shared by Codex and Claude Code.
Collaboration Model
- Codex is the lead agent for reasoning, planning, scientific judgment, review, and final synthesis.
- Claude Code is the persistent local implementation companion for repository inspection, edits, tests, refactors, and execution.
- The user should only need to talk to Codex; Claude Code reports concise execution results back to Codex.
Working Rules
- Work in the current repository root unless explicitly instructed otherwise.
- Keep changes focused on the requested task.
- Prefer reading existing code and tests before editing.
- Preserve local style, naming, and architecture.
- Run relevant checks when practical and report exact commands and outcomes.
- Do not hide blockers, uncertainty, failed commands, or skipped verification.
- Avoid dumping large file contents into chat; summarize only the necessary evidence.
Context Policy
- Treat this file as the shared project memory.
- Claude Code sessions started by cc-in-codex are persistent and resumable from the local Claude Code CLI.
- If context seems stale after a tool or MCP restart, re-read the relevant files instead of relying on memory.
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.
- 5d ago First seen · 26 lines · 235 tokens per session scan A 69875b7fc4a8
cc-in-codex AGENTS.md is an instructions file published in the GitHub repository Terry-Wang-Lynx/cc-in-codex (1 stars, last pushed 2mo ago), licensed MIT. It adds 235 tokens to every session, about $0.0012 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
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.
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.
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).