Borrowing it
Nothing to install: this file belongs to Cyruskraad/codex-claude-mcp. 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/Cyruskraad/codex-claude-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/Cyruskraad/codex-claude-mcpWrote 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/cyruskraad/codex-claude-mcp/agents-md)<a href="https://agentmods.dev/instructions/cyruskraad/codex-claude-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/cyruskraad/codex-claude-mcp/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.00659 | $0.00659 |
| Opus 5 | $0.00329 | $0.00329 |
| Sonnet 5 | $0.00132 | $0.00132 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade A, and why
codex-claude-mcp 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- codex-claude-mcp CLAUDE.md — 98% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Noodle Seed Project Context
Agent target: Codex.
Build this project as a Noodle Seed MCP server or app authored in TypeScript. Every --json command uses the canonical envelope on stdout and keeps stderr empty: one-shot commands write exactly one envelope on stdout; streaming commands write one NDJSON envelope per line. Drive the loop by parsing machine state — not by reading source or scraping human prose.
Agent-native loop
- Applicability: when the request is unrelated to the Noodle MCP server or app, follow the project's normal instructions and run no Noodle lifecycle commands.
- Route first: read the
noodle-seedskillSKILL.md, choose exactly one primary route for the requested outcome, and read that primary reference. Read supporting references only when the route or observed evidence requires them. - Discover:
noodle commands --json— every command, flag, and exit code (don't read source). - Author, when the selected route requires it: edit the configured TypeScript entrypoint — follow that route and its capability references.
- Validate:
noodle validate --json→ on failure{ok:false,error:{code,message,fix,next,errors:[{code,path,message}]}}; per-field detail is inerror.errors[]. - Repair: fix each
error.errors[]entry at itspath, re-run validate;noodle validate --fix-promptgives ready repair prose. Never freeform re-edit. - Smoke:
noodle test --json. - Continue only to the level the selected route requests: Apps/widgets use
noodle check --jsonplusnoodle devtools; hosted inspection stays read-only; hosted mutation runs only when the current user request explicitly authorizes the exact action and target. - Stale skill?
noodle agents doctor --json→noodle agents setup --write.
The exact --json/exit-code contract is in the noodle-seed skill and its references/agent-contract.md. Human-oriented command prose lives in the project README, not here.
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.
- 7d ago First seen · 39 lines · 659 tokens per session scan A 3214a45fa340
codex-claude-mcp AGENTS.md is an instructions file published in the GitHub repository Cyruskraad/codex-claude-mcp (0 stars, last pushed 11d ago), licensed MIT. It adds 659 tokens to every session, about $0.0033 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
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.
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).
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).
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.
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.