Borrowing it
Nothing to install: this file belongs to MarkDonish/round-table-workspace. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/MarkDonish/round-table-workspace/main/.claude/skills/debate/SKILL.mdgit clone --depth 1 https://github.com/MarkDonish/round-table-workspaceWrote 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.
[](https://agentmods.dev/skills/markdonish/round-table-workspace/debate)<a href="https://agentmods.dev/skills/markdonish/round-table-workspace/debate"><img src="https://agentmods.dev/badge/skills/markdonish/round-table-workspace/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.
<a href="https://agentmods.dev/skills/markdonish/round-table-workspace/debate"><img src="https://agentmods.dev/badge/skills/markdonish/round-table-workspace/debate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00035 | $0.01275 |
| Opus 5.5 | $0.00014 | $0.00510 |
| Sonnet 5.5 | $0.00007 | $0.00255 |
| Haiku 4.5 | $0.00003 | $0.00128 |
Grade A, and why
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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/debate Project Skill Adapter
This is the Claude Code project-skill entry for /debate.
It is an adapter, not the canonical implementation source. The canonical /debate sources remain:
AGENTS.mddocs/protocol-spec.md.codex/skills/debate-roundtable-skill/SKILL.md.codex/skills/debate-roundtable-skill/runtime/README.mddocs/debate-runtime-bridge.mddocs/host-adapter-architecture.mddocs/debate-skill-architecture.mddocs/agent-role-map.mddocs/reviewer-protocol.mddocs/decision-quality-rubric.mddocs/red-flags.mddocs/room-to-debate-handoff.mdschemas/debate-session.schema.jsonschemas/debate-result.schema.jsonschemas/room-to-debate-handoff.schema.jsonprompts/debate-roundtable.mdprompts/debate-reviewer.mdprompts/debate-followup.md
If this file conflicts with those sources, follow those sources and report the mismatch.
Self-Contained Path Resolution & Fallback
This skill adapter is 100% self-contained and portable:
- Primary path resolution uses repo-relative paths (e.g.
docs/...,prompts/...,schemas/...). - Canonical absolute path fallback: When running outside the repository root or in global host contexts, resolve all referenced files against
/Users/markdonish/round-table-workspace/(e.g./Users/markdonish/round-table-workspace/docs/protocol-spec.md). - All protocols, schemas, and prompt specifications are fully contained within this repository.
Trigger Boundary
Use this skill only for explicit debate mode:
/debate <topic>/debate --with ... <topic>/debate --without ... <topic>/debate --quick <topic>- a valid
/roomhandoff packet accepted by the checked-in packet preflight
Do not use this skill for ordinary chat, /room exploration before upgrade, or single-agent advice.
Operating Rules
- Treat
/debateas a round-table dispatcher and reviewer workflow, not as a personality. - Do not let participants modify runtime state directly.
- Keep
/roomhandoff one-way through the packet contract. - Do not consume historical
reports/as current handoff input. - Do not use old Windows paths as runtime entry points.
- Separate facts, inferences, uncertainty, and recommendations.
- Do not fabricate reviewer approval. If review fails, return a blocked or follow-up state.
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.
- 2mo ago First seen · 129 lines · 35 tokens per session scan A c3dcc5e424e5
debate is a skill published in the GitHub repository MarkDonish/round-table-workspace (2 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 1,275 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
requirements-writer
Use when converting PM intake into a slice SPEC.md with observable acceptance outcomes, explicit scope, and advisory sibling build dependencies.
refocusing
Use when a long-running agent may have lost the product outcome, when context was compacted, when work has crossed a major boundary, or when a fresh path-based trace is needed before the next consequential action. Not for fresh-session orientation, waking an idle seat, or checkpoints.
orchestration-team
Use when coordinating assignments, selected review boundaries, or blocked work across a rig.
oversight-team
Use when you are a seat on the oversight pod (a standing monitor-mode rig that keeps OTHER rigs healthy), configuring or running the drift detectors, or choosing whether to intervene vs escalate. Covers the pull-not-poll posture, the v0 detectors (premature-park, process-drift, off-task, token-burn), the intervention…