Borrowing it
Nothing to install: this file belongs to octanevz/codex-debate. 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/octanevz/codex-debate/main/CLAUDE.mdgit clone --depth 1 https://github.com/octanevz/codex-debateWrote 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/octanevz/codex-debate/claude-md)<a href="https://agentmods.dev/instructions/octanevz/codex-debate/claude-md"><img src="https://agentmods.dev/badge/instructions/octanevz/codex-debate/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.1 | $0.00943 | $0.00943 |
| Opus 5 | $0.00472 | $0.00472 |
| Sonnet 5 | $0.00189 | $0.00189 |
| Haiku 4.5 | $0.00094 | $0.00094 |
Grade A, and why
codex-debate 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 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.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for Claude Code and other coding agents (see AGENTS.md) when working in this repository, ordered by workflow: edit → test → lint → release.
Layout: the repository root is the marketplace (.claude-plugin/marketplace.json); each installable plugin lives under plugins/<plugin>/ with its own .claude-plugin/plugin.json, skills/<name>/ directories, README.md, LICENSE, and CHANGELOG.md. Tests, baselines, and contributor files stay at the repository root — installations copy only the plugin directory.
Editing and testing skills
- When editing a skill that has a compliance suite under
tests/<name>/, run the relevant scenarios before committing (each scenario run costs one headless Claude session); CONTRIBUTING.md documents usage. The suites load the skill via a~/.claude/skillssymlink intoplugins/<plugin>/skills/<name>/. - Some suites include a live check against a real external CLI (currently
tests/codex-debate/live-contract.sh, covering the three fragments it assembles from the skill'sreferences/prompts/:role-and-rules.md,advisory-inline-extras.md, andfenced-subject.md). Run a live check after changing what it covers or upgrading the CLI it calls, not routinely. - After changing a skill's frontmatter
description, run the triggering suite (tests/skill-triggering/run.sh; costs API calls, not in CI): compliance suites exercise behavior after invocation, not routing. (Adoptclaude plugin evalfor this once it leaves early access.) - After changing manifests or the repository layout, run the install smoke test:
tests/plugin-install/smoke.sh. - Recorded RED baselines under
tests/<name>/baselines/are historical evidence; do not re-run or overwrite them casually.
Before committing: lint and format
CI (.github/workflows/ci.yml) runs these on every push to main and every PR; run them locally first and fix findings — each must come back clean.
# all from the repository root
# shell scripts: every tracked script and test stub, same command as CI
git ls-files '*.sh' 'tests/*/bin/*' | xargs shellcheck
# report formatting diffs; fix with: shfmt -w <files>
shfmt -d .
# markdown
markdownlint-cli2 "**/*.md"
# manifests
claude plugin validate . --strict
claude plugin validate plugins/codex-debate --strict
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 · 48 lines · 943 tokens per session scan A a8b53089020f
codex-debate CLAUDE.md is an instructions file published in the GitHub repository octanevz/codex-debate (2 stars, last pushed 1mo ago), licensed MIT. It adds 943 tokens to every session, about $0.0047 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
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).
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.
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).
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.