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/ndcorder/claude-codex-team/claude-mdgit clone --depth 1 https://github.com/ndcorder/claude-codex-teamWrote 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/ndcorder/claude-codex-team/claude-md)<a href="https://agentmods.dev/instructions/ndcorder/claude-codex-team/claude-md"><img src="https://agentmods.dev/badge/instructions/ndcorder/claude-codex-team/claude-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.00223 | $0.00223 |
| Opus 5 | $0.00112 | $0.00112 |
| Sonnet 5 | $0.00045 | $0.00045 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
claude-codex-team CLAUDE.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 4d 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
Claude-Codex Team
Codex Bridge
This project develops the codex-bridge MCP server.
When planning features, designing architecture, or reviewing code, consult Codex via the codex-bridge MCP tools:
codex_planbefore writing code — get a second opinion on approachcodex_reviewafter writing code — get critical feedback on implementationcodex_askfor general brainstorming, questions, or trade-off discussions
Disagreement protocol: If Codex disagrees with your approach, surface it to the user with both perspectives. Don't silently pick a side.
Use codex_stats at the end of collaborative sessions to show the user how the collaboration went.
Benchmark
- Hand-crafted samples:
benchmark/samples/samples.json - HuggingFace samples:
npm run bench:import-hfthennpm run bench:hf - Run benchmarks:
npm run bench(single) ornpm run bench:avg(3-run average) - All benchmark commands run from the project root
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.
- 4d ago First seen · 22 lines · 223 tokens per session scan A ade1f26f0cf0
claude-codex-team CLAUDE.md is an instructions file published in the GitHub repository ndcorder/claude-codex-team (1 stars, last pushed 4mo ago), licensed MIT. It adds 223 tokens to every session, about $0.0011 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
openrouter-mcp-multimodal AGENTS.md
AGENTS.md instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
llm-context.py CLAUDE.md
Instructions for cyberchitta/llm-context.py, covering claude.md, working notes (gitignored) and draining the field notes.
seekstone CLAUDE.md
Instructions for shaqmughal/seekstone, covering claude.md, what this repo is, commands, the harness itself (run after npm install) and architecture.
Plonk AGENTS.md
AGENTS.md instructions for ostapondo/Plonk, covering agent rules, layout, adding a module, build & verify and code style.
mcp-dockhand copilot-review.instructions.md
Copilot instructions for strausmann/mcp-dockhand: When reviewing pull requests in this repository.
second-brain AGENTS.md
Instructions for LindaHaviv/second-brain, covering instructions for ai coding agents, what to read first, the rules (non-negotiable), common tasks, the sanctioned way and enforcement, not just instructions.