adversarial-debate

adversarial-debate is a skill for Claude Code from alex-jb/claude-debate. It costs 65 tokens per session (762 once invoked), scanned A, original, MIT.

A three-role debate process in which an advocate, a critic, and a judge examine a decision with genuine trade-offs.

In plain words
What is it for?
Use it when deciding whether to merge or ship something, choosing an architecture, evaluating a hire, or making another consequential technical or product decision.
Why use it?
It exposes both the strongest reasons for and against a choice before producing a considered verdict.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: positional $N argument.

Good fit Use it when deciding whether to merge or ship something, choosing an architecture, evaluating a hire, or making another consequential technical or product decision.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/alex-jb/claude-debate/adversarial-debate
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.

Any agent
npx skills add alex-jb/claude-debate --skill adversarial-debate
Clone the repo
git clone --depth 1 https://github.com/alex-jb/claude-debate

Made for: Claude Code.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/alex-jb/claude-debate/adversarial-debate/github.svg)](https://agentmods.dev/skills/alex-jb/claude-debate/adversarial-debate)
Your own site
<a href="https://agentmods.dev/skills/alex-jb/claude-debate/adversarial-debate"><img src="https://agentmods.dev/badge/skills/alex-jb/claude-debate/adversarial-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 adversarial-debate

Your own site · 80×15
<a href="https://agentmods.dev/skills/alex-jb/claude-debate/adversarial-debate"><img src="https://agentmods.dev/badge/skills/alex-jb/claude-debate/adversarial-debate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 762 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 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.00065 $0.00762
Opus 5 $0.00032 $0.00381
Sonnet 5 $0.00013 $0.00152
Haiku 4.5 $0.00006 $0.00076

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

Security

Grade A, and why

adversarial-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 12d 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.

.claude/skills/adversarial-debate/SKILL.md · 73 lines

How it starts

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

Adversarial Debate

Three-stage debate pattern for high-stakes decisions:

  1. Advocate (Haiku) — strongest case FOR the proposal
  2. Critic (Haiku) — strongest case AGAINST, rebutting the advocate
  3. Judge (Sonnet) — synthesize and return a structured verdict

Cost ~$0.003 per debate. Takes ~10-15 seconds.

When to use

Good fits:

  • Should we merge this PR given tests, blast radius, author tenure?
  • Postgres vs DynamoDB for this workload?
  • Hire or pass after the last round?
  • Ship this feature now or wait a week?
  • Trading / investment: enter or stay out?
  • Any decision with a defensible case on both sides

Bad fits:

  • Questions with one right answer (use a regular call)
  • Pure factual extraction (use a cheap single call)
  • Open-ended brainstorming (debate narrows, not expands)
  • Low-stakes decisions where $0.003 + 15s isn't worth it

Usage

from anthropic import Anthropic
from claude_debate import run_debate, DebateConfig

verdict = run_debate(
    proposal="Merge PR #42: adds Redis cache to auth middleware",
    client=Anthropic(),
    context={
        "diff_size": 340,
        "coverage": "85%",
        "author_tenure": "3 weeks",
        "prod_qps": 2400,
    },
    config=DebateConfig(
        decision_options=("APPROVE", "REQUEST_CHANGES", "DEFER"),
        criteria=["correctness", "rollback cost", "perf under load"],
    ),
)

print(verdict.decision)                    # "APPROVE"
print(verdict.confidence)                  # 72.0
print(verdict.reasoning_summary)           # one sentence
print(verdict.strongest_advocate_point)    # what was most convincing for
print(verdict.strongest_critic_point)      # what was most convincing against

Design choices worth knowing

  • Critic sees the advocate's case — so the critic's points are specific rebuttals, not independent arguments. This is what makes the debate adversarial instead of two parallel monologues.
  • Judge is explicitly asked for its tipping condition — "what evidence would flip you?" — so the verdict is falsifiable, not just assertive.
  • decision_options are bounded — the judge can't invent a new option. Forces a commit.
  • Confidence is calibrated in the prompt — 80+ = would bet on it, 50 = genuinely uncertain. Not a vibe.
  • Cost asymmetry matches reasoning asymmetry — advocate and critic are structured argument generation (Haiku is fine); judge is reasoning over conflicting evidence (Sonnet).

Read the full file on GitHub · 73 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. 12d ago First seen · 73 lines · 65 tokens per session scan A 2021bdd9b206

Subscribe to this mod's changes

adversarial-debate is a skill published in the GitHub repository alex-jb/claude-debate (2 stars, last pushed 4mo ago), licensed MIT. It adds 65 tokens to every session and 762 once invoked, about $0.0003 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

analytics-strategy

Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement.…

rampstackco/claude-skills · 126 tokens

content-strategy

Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. Use this skill whenever the user wants to plan a content program, define content pillars, build an editorial calendar, structure topic clusters, set up content governance, or align…

rampstackco/claude-skills · 120 tokens

incident-response

Manage active production incidents through detection, triage, mitigation, communication, and resolution with structured roles and decision-making. Use this skill whenever the user has an active incident, a production issue, a service outage, a security incident, or needs to plan incident response procedures. Triggers…

rampstackco/claude-skills · 117 tokens

stakeholder-communication

Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…

rampstackco/claude-skills · 103 tokens

review-work

Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.

code-yeongyu/oh-my-openagent · 63 tokens

agb-begriff-vorformuliert-305

Für AGB Begriff Vorformuliert 305: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: agb-begriff-vorformuliert-305.

Klotzkette/claude-fuer-deutsches-recht · 68 tokens