A guided debate between Claude and OpenAI Codex about a software design decision. It produces a decision brief for you to evaluate instead of writing code.

Use it to compare two design positions and make a reasoned engineering decision.

It helps expose trade-offs and competing viewpoints before you commit to an approach.

debate — Command for coding agents by ccplugins: A guided debate between Claude and OpenAI Codex about…

Install

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.

agentmods

npx agentmods add commands/ccplugins/awesome-claude-code-plugins/debate

Clone the repo

git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins

Or install claudex, the plugin that ships this one along with the rest of its 1 skill, 6 commands.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/ccplugins/awesome-claude-code-plugins/debate.svg)](https://agentmods.dev/commands/ccplugins/awesome-claude-code-plugins/debate)

Your own site

<a href="https://agentmods.dev/commands/ccplugins/awesome-claude-code-plugins/debate"><img src="https://agentmods.dev/badge/commands/ccplugins/awesome-claude-code-plugins/debate.svg" alt="Measured on agentmods" height="20"></a>

Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,486 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00018	$0.01486
Opus 5	$0.00009	$0.00743
Sonnet 5	$0.00004	$0.00297
Haiku 4.5	$0.00002	$0.00149

Measured yesterday against content hash d735ae5d4c05, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

debate 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

debate — 100% identical, 0 lines differ

plugins/claudex/commands/debate.md · 111 lines

How it starts

The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are running ClauDex debate — a structured argument between Claude Code (you, 🧡) and OpenAI Codex (🖤) over a real design decision. Nobody writes code here; the deliverable is a decision brief the user can arbitrate.

Sign-off contract: the closing line argued with love by ClauDex 🧡🖤 appears ONLY when Codex delivered both its opening position and its rebuttal — and it is REQUIRED then (an earned, unsigned run breaks the contract just like an unearned, signed one). Refusal, interruption, or an empty motion all end UNSIGNED. The verb is "argued" — this command builds nothing and reviews no diff; only the /claudex loop signs "built", only reviews sign "reviewed".

Preflight — it takes two to ClauDex

Run codex --version and check auth (codex login status or the equivalent for the installed version). If either fails, STOP before any framing or arguing and reply with exactly:
It takes two to ClauDex. 🧡 Claude is here — 🖤 Codex is not, and a one-model debate is just a monologue. Fix it in two lines, then come back for the argument:
```
npm i -g @openai/codex
codex login
```
The motion. "$ARGUMENTS" must state a decision. If it is empty, STOP unsigned and ask for one, with two examples of a good motion — a decision with real options ("Postgres vs SQLite for this app"), not a topic ("databases").

(No git preflight — a debate needs a question, not a diff. If you happen to be inside a relevant repo, the codebase is context, not a requirement.)

The debate

Frame the motion. Sharpen "$ARGUMENTS" into a decision question with 2–3 concrete options. If the user named a topic rather than a choice, propose the decision you believe they meant and say what you assumed. Gather grounding: if the current repo is relevant, read the few files that matter and note the hard constraints (existing stack, scale hints, deploy target). Compress all of it into a short written brief — motion, options, constraints. Keep it under a page; a debate is not a survey.
Claude's opening (yours). Pick the option you would actually choose and argue it: your three strongest arguments, the biggest risk of your own choice (steelman honesty), and what evidence would change your mind. Write it BEFORE consulting Codex, so your position is genuinely independent.
Codex's opening — safe transport. Write the brief from step 1 to a temp file (e.g. $TMPDIR/claudex-debate.md) — the motion, options, and constraints only, NOT your position; never inline content in the shell command. Then, with a hard timeout of ~10 minutes:

Read the full file on GitHub · 111 lines

Changes

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 · 111 lines · 18 tokens per session scan A d735ae5d4c05

Subscribe to this mod's changes

debate is a command published in the GitHub repository ccplugins/awesome-claude-code-plugins (931 stars, last pushed 23d ago), licensed Apache-2.0. It adds 18 tokens to every session and 1,486 once invoked, about $0.0001 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-09-03.

Code review Planning awesome-claude-code awesome-list awesome-plugins awesome-resources claude-code claude-code-commands

create-pull-request

Provides comprehensive PR creation guidance with GitHub CLI, enforcing title conventions, following template structure, and offering concrete command examples with best practices.

xbim08/awesome-claude-code-plugins · 27 tokens

pr-issue-resolve

Follow these steps to analyze suggested changes (e.g., review comments, inline suggestions, or requested modifications) in a GitHub Pull Request (PR) and resolve them efficiently. The goal is to review, understand, plan fixes, apply changes, test, and update the PR while maintaining code quality and collaboration.

xbim08/awesome-claude-code-plugins · 14 tokens

openapi-expert

Use this agent when you need to update, synchronize, or validate the OpenAPI specification (openapi.yml) against the actual REST API implementation. This includes adding new endpoints, updating request/response schemas, fixing discrepancies between the spec and code, or ensuring complete API documentation coverage.

xbim08/awesome-claude-code-plugins · 61 tokens

debate