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/sendbird/cc-plugin-codex/agents-mdgit clone --depth 1 https://github.com/sendbird/cc-plugin-codexWhat 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.00126 | $0.00126 |
| Opus 5 | $0.00063 | $0.00063 |
| Sonnet 5 | $0.00025 | $0.00025 |
| Haiku 4.5 | $0.00013 | $0.00013 |
Grade A, and why
cc-plugin-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 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.
What it actually says
Repository guidance
- This is a Node.js 18+ ESM Codex plugin. Keep behavior portable across macOS, Linux, and native Windows.
- Fix shared behavior at the earliest common boundary, usually in
scripts/lib/; do not add caller-specific workarounds. - When changing a skill or runtime contract, keep
skills/,internal-skills/,scripts/, and the matching tests in sync. - Run
npm run checkbefore merging. - For releases, update
CHANGELOG.mdand keeppackage.jsonand.codex-plugin/plugin.jsonversions synchronized.
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 · 8 lines · 126 tokens per session scan A 4f75643e743e
cc-plugin-codex AGENTS.md is an instructions file published in the GitHub repository sendbird/cc-plugin-codex (182 stars, last pushed 2d ago), licensed Apache-2.0. It adds 126 tokens to every session, about $0.0006 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
aider-desk AGENTS.md
Instructions for hotovo/aider-desk, covering agents.md, common commands, development, type checking and linting and formatting.
crystal CLAUDE.md
Instructions for stravu/crystal, covering crystal - multi-session claude code manager, project overview, references, implementation status: ✅ complete and ✅ implemented features.
easy-cheese python.instructions.md
Instructions for paulnsorensen/easy-cheese, covering hard rules, what to flag and what not to flag.
claude-bridge AGENTS.md
Instructions for kadaba/claude-bridge, covering agents.md — using claude-bridge from any ai coding cli, two independent channels, 1. coordination (the conversation), 2. file transfer (the bytes) — same for every tool and workflows.
AmbyKit CLAUDE.md
Instructions for ambystechcom/AmbyKit, covering claude code — notes for the ambykit repo and claude-specific.
sugar AGENTS.md
AGENTS.md instructions for roboticforce/sugar, covering sugar - agents.md, git branching rules (strict), always create branches from develop, after work is complete and then create pr targeting develop.