ccc-debate SKILL.md skillA

ccc-debate from kevinzai/commander is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add kevinzai/commander/ccc-debate@git:20261013.fbe187d

Pins git:20261013.fbe187d in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: kevinzai/commander
Path: commander/cowork-plugin-codex/skills/ccc-debate/SKILL.md
Versions recorded: 5
Latest version: git:20261013.fbe187d, committed Oct 13, 2026
First version recorded: Jul 1, 2026
Size: 7,590 bytes
Repository stars: 6
License: MIT

Adversarial multi-agent debate: lens agents (security, performance, architecture, product, contrarian) argue and cross-examine one design, plan or diff, then a judge rules ship, revise or block. Use when a decision is costly to reverse, a diff touches auth or billing, or the user types $ccc-debate.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# $ccc-debate — stress-test before reality does

**CC Commander** · $ccc-debate · surviving objections and a 🟢 ship / 🟡 revise / 🔴 block verdict on one design, plan or diff, without the transcript in your context.

Lens agents argue; the judge rules; the user decides. This is the dialectic form of `rules/workflow-first.md`: delegate the arguing, keep the ruling.

## When to use / when not to

- Use for expensive-to-reverse design or architecture calls, diffs where a silent flaw is costly (auth, billing, migrations), plans worth testing from for/against angles before locking, and "am I missing something?" checks on a spec.
- Skip for routine edits, single-file fixes, obvious answers, or work where speed beats rigor. Without a concrete target (a doc, a plan, a diff) there is nothing to argue.
- Token spend is lenses × rounds. Scope to one target; default to 3 lenses and 2 rounds.

## What happens

### 1. Resolve the target

- A path argument: confirm it exists with `test -f <path>` and read it.
- `diff`, or no argument inside a repo with changes: run `git diff --stat HEAD` and use the uncommitted diff as the target.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add kevinzai/commander/ccc-debate@sha256:5f3b64bc09d84539

The line at the top of this page pins the label git:20261013.fbe187d, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

[![mdr](https://markdownregistry.com/badge/art_rj2la7g2u3wnjjyr.svg)](https://markdownregistry.com/a/art_rj2la7g2u3wnjjyr)

1 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 5 versions of this file, between Jul 1, 2026 and Oct 13, 2026, about one every 26 days.

version	committed	commit	size	audit
git:20261013.fbe187d latest	2026-10-13	fbe187d	7,590 B	A	view · diff
git:20260722.9d3ab82	2026-07-22	9d3ab82	8,370 B	A	view · diff
git:20260716.930d05a	2026-07-16	930d05a	8,151 B	A	view · diff
git:20260707.947ab2f	2026-07-07	947ab2f	8,152 B	A	view · diff
git:20260701.1f4accc	2026-07-01	1f4accc	7,983 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (7590 bytes)
pass: No zero-width or bidi control characters
pass: No instruction hidden inside an HTML comment
pass: No link to an exfiltration or paste host
pass: No credential-shaped string
pass: No instruction to send local credentials anywhere
pass: No text hidden with inline styles
pass: No prompt-injection phrasing
pass: No curl or wget piped into a shell
pass: No recursive delete of root, home or parent
pass: No instruction to read or print local credentials
pass: No base64 blob over 200 characters
pass: No link to a raw IP address
pass: No script tag

Source

GitHub

kevinzai/commander · 6 stars · license MIT · pushed 2026-11-08 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_rj2la7g2u3wnjjyr
GET https://markdownregistry.com/api/v1/resolve?ref=kevinzai/commander/ccc-debate
GET https://markdownregistry.com/api/v1/blob/5f3b64bc09d845398fca5c97d3804c41d64fd47acce00d2cfa7e8f91cbb47728

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from kevinzai/commander

mintlify SKILL.md skill

kevinzai/commander · .agents/skills/mintlify/SKILL.md · Build and maintain documentation sites with Mintlify. Use when

v1.0 · audit A · 6 stars

.cursorrules Cursor rule

kevinzai/commander · .cursorrules

git:20260327.b10b207 · audit A · 6 stars

AGENTS.md AGENTS.md file

kevinzai/commander · AGENTS.md