debate-orchestrator

debate-orchestrator is a skill for Claude Code from urav06/dialectic. It costs 41 tokens per session (2,218 once invoked), scanned A, original, MIT.

A skill that coordinates formal debates between a proposition side and an opposition side. It tracks debate rounds and whether participants must submit arguments or receive judgment.

In plain words
What is it for?
Use it to run opening arguments and rebuttals, coordinate debaters and judges, save debate progress, and advance a chosen number of exchanges.
Why use it?
It keeps multi-round debates organized, allows both sides to work at the same time, and can continue after an interruption.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Part of the dialectic plugin — 1 skill, 3 commands, 2 agents shipped together

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 skills/urav06/dialectic/debate-orchestrator
Any agent
npx skills add urav06/dialectic --skill debate-orchestrator
Clone the repo
git clone --depth 1 https://github.com/urav06/dialectic

Made for: Claude Code.

Or install dialectic, the plugin that ships this one along with the rest of its 1 skill, 3 commands, 2 agents.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/urav06/dialectic/debate-orchestrator.svg)](https://agentmods.dev/skills/urav06/dialectic/debate-orchestrator)
Your own site
<a href="https://agentmods.dev/skills/urav06/dialectic/debate-orchestrator"><img src="https://agentmods.dev/badge/skills/urav06/dialectic/debate-orchestrator.svg" alt="Measured on agentmods" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,218 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00041 $0.02218
Opus 5 $0.00020 $0.01109
Sonnet 5 $0.00008 $0.00444
Haiku 4.5 $0.00004 $0.00222

Measured 5d ago against content hash 40c703e4f14e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

debate-orchestrator 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 5d ago.

The scan reads SKILL.md. This mod also ships 7 executable files (debate_ops/__init__.py, debate_ops/__main__.py, debate_ops/debater.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.claude/skills/debate-orchestrator/SKILL.md · 269 lines

How it starts

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

Debate Orchestrator

Manages formal debate execution through deterministic state tracking and resumability.

State Machine

Debates cycle through 2 phases per exchange:

current_phase Action Required
awaiting_arguments Spawn both debaters in parallel
awaiting_judgment Spawn judge to evaluate all new arguments

After judgment: cycle repeats with current_exchange incremented.

Key Properties:

  • No "complete" state - orchestrator decides when to stop based on requested exchange count
  • Parallel execution - both sides argue simultaneously each exchange
  • Resumable - read state, execute required action, repeat
  • Exchange 0 is special (opening) - both sides produce 3 independent arguments
  • Exchange 1+ are rebuttal - sides produce single arguments with attacks/defends

Running Exchanges

1. Read State

Check {debate}/debate.md frontmatter (JSON format):

{
  "current_exchange": 0,
  "current_phase": "awaiting_arguments"
}

Extract motion from the # Motion section (first markdown heading after frontmatter).

2. Determine Exchange Type

Opening Exchange: current_exchange == 0

  • Both debaters produce 3 independent arguments simultaneously
  • Judge scores all 6 arguments

Rebuttal Exchange: current_exchange >= 1

  • Both debaters produce 1 argument simultaneously
  • Judge scores both new arguments

3. Execute Based on Phase + Exchange Type

Opening Exchange (Exchange 0)

When current_exchange == 0 and current_phase == awaiting_arguments:

Load template:

Read templates/debater-opening.md from this skill's directory.

Spawn both debaters in parallel:

Use a single message with two Task tool invocations to spawn both debaters simultaneously.

For each side (proposition and opposition):

  1. Substitute placeholders in template:

    • {motion}: Extracted motion text
    • {side}: Side name (proposition or opposition)
  2. Spawn debater:

    Use Task tool with subagent_type: "debater"
    Prompt: [substituted template content]
    

Read the full file on GitHub · 269 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. 5d ago First seen · 269 lines · 41 tokens per session scan A 40c703e4f14e

Subscribe to this mod's changes

debate-orchestrator is a skill published in the GitHub repository urav06/dialectic (6 stars, last pushed 9mo ago), licensed MIT. It adds 41 tokens to every session and 2,218 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

using-dinf

WHAT: the D∞ notation — the ⟨parts | Ω⟩ shape every durable teaching, framework, plan, and joke has — plus the three operators over it (FACTOR, ADJOIN, CHRISTEN) and the dinf CLI that makes the missing-closure defect machine-catchable. WHEN: when stuck; when a plan feels like unjoined parts; when two frames are…

sancovp/dinf · 118 tokens

teach-revision

Instructional. Activate when a learner wants to be walked through improving their own draft so they learn to do it themselves, not just handed a fixed version. Common phrasings: "Walk me through improving this so I learn to do it myself", "Teach me why these edits work". Expected inputs: the learner's draft, the…

OC-NeuralSense/reader-first-writing-skills · 166 tokens

tokenomics-method

Use when a builder wants to learn or be reminded of the tokenomics method: spending model capability like a scarce budget through tiered routing, spec-based handoffs, and a living playbook. Teaches the thesis, the four layers, the four switchpoints, the routing test, and the lane-scarcity rule. Pure knowledge; takes…

slopstopper/tokenomics · 76 tokens

cu-lengths-attention-flow

Bilingual guide for understanding how culengths controls attention behavior across ViT and LLM stages, and how patchpositions scope differs between the two.

EvolvingLMMs-Lab/LLaVA-OneVision-2 · 35 tokens

elixir-idioms

OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.

oliver-kriska/claude-elixir-phoenix · 44 tokens

engineering-onboarding

Create an onboarding guide for an engineer joining a team that consumes the design system. Trigger when someone says: onboard new engineer, developer getting started guide, new engineer guide, engineering onboarding, first day for developers, frontend onboarding, or anything about helping an engineer new to the team…

murphytrueman/design-system-ops · 68 tokens