debate-report

A command that turns a recorded debate into a written analysis and an argument-graph image. An argument graph is a diagram showing how claims support or challenge one another.

In plain words
What is it for?
Use it to report on a selected debate, summarize its arguments, and create a PNG visualization from a Mermaid graph file.
Why use it?
It gathers the debate’s conclusions and structure in one report, so you do not have to review every argument manually. It can also identify when the required diagram tool is unavailable.

Command for Claude Code

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/urav06/dialectic/debate-report
Clone the repo
git clone --depth 1 https://github.com/urav06/dialectic

Made for: Claude Code.

Per session 8 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,109 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 $0.00008 $0.01109
Opus 5 $0.00004 $0.00554
Sonnet 5 $0.00002 $0.00222
Haiku 4.5 $0.00001 $0.00111

Measured 2d ago against content hash 0885072b813b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

debate-report 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 2d 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/commands/debate-report.md · 146 lines

How it starts

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

Generate Debate Report

Analyzes the debate and generates a comprehensive report with argument graph visualization.

Arguments

  • $1: Debate slug (optional if only 1 debate exists)

Step 1: Determine Debate

If $1 provided:

  • Use it

If no $1:

  • List debates
  • If 0: "No debates found."
  • If 1: Auto-use that debate
  • If 2+: "Which debate? {list}"

Step 2: Convert Argument Graph to PNG

Try to convert {debate}/argument-graph.mmd to PNG image:

mmdc -i {debate}/argument-graph.mmd -o {debate}/argument-graph.png -t dark -b transparent -s 4

If conversion succeeds:

  • Note: "✓ Graph visualization created"
  • Set image_exists = true
  • Continue to Step 3

If conversion fails:

Check if mmdc (mermaid-cli) is installed:

which mmdc || command -v mmdc

If not installed, present options:

"Graph visualization requires mermaid-cli (not currently installed).

Choose how to proceed:

1. Install and retry - Install mermaid-cli then run this command again

  • npm: npm install -g @mermaid-js/mermaid-cli
  • Docker: docker pull minlag/mermaid-cli (requires creating a shell alias for mmdc)

2. Convert manually - Convert the graph yourself and continue

  • Copy contents of {debate}/argument-graph.mmd
  • Convert online at: https://mermaid.live
  • Download PNG and save as {debate}/argument-graph.png
  • Reply: 'Image provided, continue'

3. Skip visualization - Generate report without the graph image

  • Reply: 'Skip image, continue'"

Wait for user input:

  • If "1": Exit with message "Install mermaid-cli and re-run /debate-report {slug}"
  • If "2": Set image_exists = true, continue to Step 3
  • If "3": Set image_exists = false, continue to Step 3

Step 3: Generate Comprehensive Report

Use Task tool with subagent_type "general-purpose" to generate analysis:

Prompt:

Generate a comprehensive debate report for the debate at {debate}/.

Read and analyze:
- Motion from @{debate}/debate.md
- All arguments in @{debate}/arguments/
- Scores from @{debate}/scores.json
- Debate state and cumulative scores from @{debate}/debate.md frontmatter

Your task is to write a compelling, high-level analysis in **500-600 words** that captures the intellectual battle and hooks readers. This is a summary for someone who hasn't read the full debate yet—make it engaging and insightful, not exhaustive.

**Required structure:**

# [Motion Title]

## The Question
1-2 sentences capturing what's at stake and why it matters

## The Clash
100-150 words on the fundamental disagreement. What core assumptions or frameworks divide the sides?

## Turning Points
150-200 words on 2-3 key moments that shifted the debate's trajectory. Focus on the most dramatic or intellectually significant developments.

## The Verdict
100-150 words: Final scores (zero-sum totals), strongest/weakest arguments with IDs, and your assessment of who won and why

{if image_exists:}
## Argument Graph

![Argument Graph](./argument-graph.png)
{/if}

**Style guidelines:**
- Use rich markdown: headings (##, ###), **bold**, *italic*
- Match tone to debate topic (serious debates = analytical tone, lighter topics = can be more engaging)
- Strictly avoid em-dashes and en-dashes
- Focus on clarity and intellectual substance over exhaustive detail
- 500-600 words total (strictly enforced)

Output ONLY the complete markdown content for the README.md file.

Read the full file on GitHub · 146 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. 2d ago First seen · 146 lines · 8 tokens per session scan A 0885072b813b

Subscribe to this mod's changes

debate-report is a command published in the GitHub repository urav06/dialectic (6 stars, last pushed 8mo ago), licensed MIT. It adds 8 tokens to every session and 1,109 once invoked, about $0.0000 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.