Home / kevinzai / commander · GitHub

ccc-orchestrate SKILL.md skillA

ccc-orchestrate 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-orchestrate@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-orchestrate/SKILL.md
Versions recorded: 5
Latest version: git:20261013.fbe187d, committed Oct 13, 2026
First version recorded: Jul 10, 2026
Size: 9,481 bytes
Repository stars: 6
License: MIT

Write a goal file, run it on a separate executor (Codex GPT-6 or a Sonnet subagent) in an isolated worktree, then verify every acceptance criterion. Use when a task benefits from a different executor and independent verification.

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-orchestrate — plan, delegate, verify

**CC Commander** · $ccc-orchestrate · a goal file with testable criteria, executed elsewhere, verified here

The orchestrator is the calling session (the `fable` or `opus` tier, whichever the user runs; the selected model is preserved). It writes the goal file and verifies the result. It does not write production code in this mode. The executor is a separate runtime that reads the goal file as its whole brief.

## When to use / when not to

- Use when the request is fuzzy enough that compressing it into a spec pays off, and an independent executor plus a checklist-based verification adds confidence.
- Use when the user asks for Codex to do the implementation, or for a cross-vendor second pair of hands.
- Do not use for a one-line edit; do it inline.
- Do not use when the user wants to stay in one vendor and one session; use `$ccc-plan-exec`.

## Executors

| Executor id | Runs on | Use for |
|---|---|---|
| `codex-gpt-6-astra` | `codex exec -m gpt-6-astra` | deep work: migrations, tricky concurrency, security-sensitive changes |
| `codex-gpt-6.1-sol` | `codex exec -m gpt-6.1-sol` | default implementation executor |
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add kevinzai/commander/ccc-orchestrate@sha256:ae260aed159e02b8

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_xfjegpdkhcmkqvep.svg)](https://markdownregistry.com/a/art_xfjegpdkhcmkqvep)

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

Versions

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

version	committed	commit	size	audit
git:20261013.fbe187d latest	2026-10-13	fbe187d	9,481 B	A	view · diff
git:20260728.ab5edc5	2026-07-28	ab5edc5	9,656 B	A	view · diff
git:20260722.9d3ab82	2026-07-22	9d3ab82	9,662 B	A	view · diff
git:20260710.7b3195c	2026-07-10	7b3195c	9,530 B	A	view · diff
git:20260710.c2a3d00	2026-07-10	c2a3d00	8,883 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 (9481 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_xfjegpdkhcmkqvep
GET https://markdownregistry.com/api/v1/resolve?ref=kevinzai/commander/ccc-orchestrate
GET https://markdownregistry.com/api/v1/blob/ae260aed159e02b8ac07146e3b9e44d634b68281ed0e712d5a8f0e6ddd781950

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