octo-debate

octo-debate is a command for Claude Code from CES-Ltd/Lumi. It costs 21 tokens per session (568 once invoked), scanned A, a copy of octo-debate, MIT.

A command for running structured debates between Claude, Sonnet, Gemini, and Codex, which are different AI models. It requires sending the question to external providers and following a multi-step debate process.

In plain words
What is it for?
Use it to compare AI viewpoints on a question through provider checks, clarification, debate rounds, and a final synthesis.
Why use it?
It gathers several model responses and organizes them into a debate instead of relying on one model's answer.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents; names the AskUserQuestion tool; mentions Codex.

Part of the octo plugin — 10 skills, 47 commands shipped together

Good fit Use it to compare AI viewpoints on a question through provider checks, clarification, debate rounds, and a final synthesis.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/ces-ltd/lumi/octo-debate
View source ↗ CES-Ltd/Lumi
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.

Clone the repo
git clone --depth 1 https://github.com/CES-Ltd/Lumi

Made for: Claude Code.

Or install octo, the plugin that ships this one along with the rest of its 10 skills, 47 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.

agentmods badge for octo-debate

README.md
[![agentmods](https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-debate/github.svg)](https://agentmods.dev/commands/ces-ltd/lumi/octo-debate)
Your own site
<a href="https://agentmods.dev/commands/ces-ltd/lumi/octo-debate"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-debate/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for octo-debate

Your own site · 80×15
<a href="https://agentmods.dev/commands/ces-ltd/lumi/octo-debate"><img src="https://agentmods.dev/badge/commands/ces-ltd/lumi/octo-debate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 568 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 89% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00021 $0.00568
Opus 5 $0.00010 $0.00284
Sonnet 5 $0.00004 $0.00114
Haiku 4.5 $0.00002 $0.00057

Measured 10d ago against content hash 0c69f64b8ef4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

octo-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 10d 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.

Origin

This is a copy

89% identical to octo-debate — 16 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

resources/seed/octopus/commands/octo-debate.md · 57 lines

How it starts

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

Debate

Structured four-way AI debates between Claude, Sonnet, Gemini, and Codex.

🤖 INSTRUCTIONS FOR CLAUDE

MANDATORY COMPLIANCE — DO NOT SKIP

When the user explicitly invokes /octo:debate, you MUST execute the structured debate workflow below. You are PROHIBITED from answering the question directly, skipping the multi-provider debate, or deciding the topic is "too simple" for a four-way debate. The user chose this command deliberately — respect that choice.

EXECUTION MECHANISM — NON-NEGOTIABLE

You MUST dispatch work to external providers (Codex, Gemini, etc.) for this command. You are PROHIBITED from:

  • ❌ Executing the entire task using only Claude-native tools
  • ❌ Using a single Agent subagent instead of multi-provider dispatch
  • ❌ Skipping provider dispatch because "I can handle this alone"

Multi-LLM orchestration is the purpose of this command. Single-model execution defeats its purpose.


Execution

  1. Follow the skill-debate instructions (Steps 1-7) exactly.
  2. Start with Step 1: check provider availability and display the visual indicator banner.
  3. Step 2: ask clarifying questions via AskUserQuestion before proceeding.
  4. Steps 3-5: parse arguments, set up debate folder, conduct rounds with all four participants (Gemini CLI, Codex CLI, Sonnet Agent, Claude/Opus).
  5. Steps 6-7: write final synthesis and present results to the user.
  6. Apply quality gates and cost tracking from skill-debate throughout.

Post-Completion — Interactive Next Steps

CRITICAL: After the debate completes, you MUST ask the user what to do next. Do NOT end the session silently.

AskUserQuestion({
  questions: [
    {
      question: "The debate is complete. What would you like to do next?",
      header: "Next Steps",
      multiSelect: false,
      options: [
        {label: "Run another round", description: "Continue the debate with additional rounds"},
        {label: "Act on the winner", description: "Proceed with the winning argument's recommendation"},
        {label: "Debate a related topic", description: "Start a new debate on a follow-up question"},
        {label: "Export the synthesis", description: "Save the debate results as a document"},
        {label: "Done for now", description: "I have what I need"}
      ]
    }
  ]
})

Read the full file on GitHub · 57 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.

  1. 10d ago First seen · 57 lines · 21 tokens per session scan A 0c69f64b8ef4

Subscribe to this mod's changes

octo-debate is a command published in the GitHub repository CES-Ltd/Lumi (31 stars, last pushed 4mo ago), licensed MIT. It adds 21 tokens to every session and 568 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to octo-debate, differing in 16 lines, and is treated as a copy.