multiagent-debate

multiagent-debate is a skill for Claude Code, Codex from yogsoth-ai/stress-test. It costs 53 tokens per session (1,290 once invoked), scanned A, original, Apache-2.0.

A structured process where several AI agents argue different sides of a claim, idea, research question, or experiment design. It uses debate rounds to test whether the artifact withstands criticism.

In plain words
What is it for?
Use it to challenge hypotheses, compare approaches, review research questions, or stress-test experiment designs.
Why use it?
It exposes weak assumptions, missing evidence, and disagreements before you rely on a conclusion.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

Good fit Use it to challenge hypotheses, compare approaches, review research questions, or stress-test experiment designs.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/yogsoth-ai/stress-test/multiagent-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 yogsoth-ai/stress-test --skill multiagent-debate
Clone the repo
git clone --depth 1 https://github.com/yogsoth-ai/stress-test

Made for: Claude Code, Codex.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/yogsoth-ai/stress-test/multiagent-debate/github.svg)](https://agentmods.dev/skills/yogsoth-ai/stress-test/multiagent-debate)
Your own site
<a href="https://agentmods.dev/skills/yogsoth-ai/stress-test/multiagent-debate"><img src="https://agentmods.dev/badge/skills/yogsoth-ai/stress-test/multiagent-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 multiagent-debate

Your own site · 80×15
<a href="https://agentmods.dev/skills/yogsoth-ai/stress-test/multiagent-debate"><img src="https://agentmods.dev/badge/skills/yogsoth-ai/stress-test/multiagent-debate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,290 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.00053 $0.01290
Opus 5.5 $0.00021 $0.00516
Sonnet 5.5 $0.00011 $0.00258
Haiku 4.5 $0.00005 $0.00129

Measured 1mo ago against content hash 41095b8a952d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

multiagent-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 1mo 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.

skills/multiagent-debate/SKILL.md · 120 lines

How it starts

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

Multi-Agent Debate Campaign

Core question: Can this artifact survive structured adversarial debate?

Methodology Sources

  • Irving et al. (2018) — AI Safety via Debate
  • Du et al. (2023) — Society of Mind multi-agent sharing
  • Liang et al. (2023) — MAD (Multi-Agent Debate)
  • Toulmin (1958) — Argumentation model (claim, ground, warrant, backing, qualifier, rebuttal)
  • D3 framework — Deliberate, Debate, Decide

Strategy Routing

Artifact Type Primary Strategy Fallback Strategy
hypothesis, claim critic-defender-judge adversarial-escalation
research-question multi-perspective-panel society-of-mind
idea, approach society-of-mind courtroom-structured
experiment-design courtroom-structured critic-defender-judge
gap multi-perspective-panel adversarial-escalation

Budget Table

Parameter S (Quick) M (Standard) L (Deep)
Debate rounds 4 8 12
Participating agents 3 5 8
Coverage dimensions 3 5 7
External evidence searches 2 5 10

Tactics

  • dialectical-escalation — Progressive pressure escalation based on confidence thresholds
  • perspective-rotation — Sequential perspective evaluation with divergence aggregation
  • evidence-tournament — Evidence gathering, cross-examination, and quality judgment

Context Management

Each subagent operates in isolated context. The debate-architect designs structure before execution. Transcripts are passed between rounds via structured markdown. Saturation detection terminates when novelty drops below threshold.

Output

Produces DebateVerdict containing: survival assessment, key vulnerabilities, confidence score, debate transcript summary, and recommended mitigations.

Available Strategies

Optional, no fixed order; the final leaf is always a sop.

Strategy When to use
adversarial-escalation Strategy: Progressive pressure escalation — starts with surface-level challenges and escalates to fundamental assumption attacks based on defender confidence decay.
courtroom-structured Strategy: Legal adversarial structure — prosecution presents case, defense responds, evidence is cross-examined, judge delivers verdict. Emphasizes evidence quality and procedural rigor.
critic-defender-judge Strategy: Classic triangular debate — Critic attacks, Defender responds, Judge adjudicates. Based on Irving AI Safety via Debate with Toulmin argumentation structure.
multi-perspective-panel Strategy: Multi-stakeholder review panel — diverse expert perspectives evaluate artifact simultaneously, then synthesize through structured deliberation.
society-of-mind Strategy: Multi-agent collaborative debate based on Du et al. Society of Mind. Agents share perspectives iteratively until convergence or divergence is detected.

Read the full file on GitHub · 120 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. 1mo ago First seen · 120 lines · 53 tokens per session scan A 41095b8a952d

Subscribe to this mod's changes

multiagent-debate is a skill published in the GitHub repository yogsoth-ai/stress-test (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 53 tokens to every session and 1,290 once invoked, about $0.0002 per session on Opus 5.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.

Related

Other skills, from other repositories