Skills
81 click-first /ccc-* slash commands. Every menu is a native chip picker — no typing, no YAML, no syntax to memorize.
agent_id — finished agents finally show finished · keyless everywhere: no license keys on any shipped surface · rtk vendor security bump (v0.44.2) · root npm audit: 0·
v7.4.1
stable · 2026-07-29 · /ccc-update + /ccc-doctor detect Desktop-managed (account-synced) installs·
three install modes detected (CLI marketplace / Desktop-managed / dev checkout) · reads the Desktop copy’s real version · mode-correct upgrade guidance·
v7.4.0
stable · 2026-07-28 · One Commander — four decks become one console, with a prompt bar to your live Claude session·
/ccc-console (82nd skill) · inline widget + shareable snapshot from ONE renderer · Memory (claude-mem, optional) + History tabs · existing deck URLs preserved · auto-open (off-switchable) · prompt-injection-resistant by construction — chips are allowlisted literals, memory text renders inert·
v7.3.2
stable · 2026-07-28 · Anthropic + Codex CLI only — no Gemini, no local-LLM routing·
executor preference claude → codex · gemini-fallback rewritten as large-context (Opus 5 is 1M natively, so the old “escape Claude’s 200K limit” premise is gone) · local-LLM docs page removed·
v7.3.1
stable · 2026-07-28 · Claude Opus 5 end to end — plus two real bug fixes·
default pin claude-opus-5 (no [1m] — 1M is default and max) · effort defaults to high, escalate deliberately · delegation gains a size threshold · /ccc-doctor had been failing on healthy installs since v6.0 · complexity ≥93 emitted an invalid --effort ultra, so the hardest tasks failed at dispatch · all 19 vendors refreshed·
v6.8.3
stable · 2026-07-17 · Mission Control gets a Charts strip, a claude-mem History panel, and complete Claude + Codex rosters·
zero-dep inline-SVG cost/agents/tasks/failures charts · Codex roster rows derived from delegation events, marked "inferred" · metrics.jsonl daily rollup + per-skill breakdown·
v6.8.2
stable · 2026-07-16 · Commander Cockpit — every Commander tool clickable inside one artifact·
/ccc-browse → 🎛️ five tabs: browse, ideas, prompt-enhance, analytics, agent manager · skill-runs logger (42nd hook handler)·
v6.8.0
stable · 2026-07-16 · Commander Mission Control — live agent dashboard inside Claude Code Desktop, built for non-coders·
/ccc-mission-control — roster, delegation flow, task board, live event feed · v6.8.1 adds Claude + Codex source tracking and a Suggestions panel·
78 plugin skills · 22 agents · 23 hooks (42 handlers) · core free forever · MIT licensed·
v6.7.3
/ccc-prompt-fix — auto prompt fixer · claude-code-library — 52-prompt library·
v6.7.2
/ccc-spawn — click-first spawn hub·
v6.7.1
/ccc-broadcast — outbound status relay·
v6.7.0
/ccc-relay — cross-session loop chaining · /ccc-smb-ops — small-business ops domain·
v6.6.0
stable · 2026-07-10 · Engagement Engine — hook delivery rebuilt on documented output fields, always-on suggestions surface as AskUserQuestion chips·
/ccc-claudemd — CLAUDE.md auto-audit, AUQ-gated fixes (72nd plugin skill)·
77 plugin skills · verifier-separation + worktree isolation enforced across every write path·
v6.4.0
stable · 2026-07-07 · The Fable Method — 12 enforceable gates so any model produces Fable-shaped results·
/ccc-fable — master switch: on · status · audit · off·
77 plugin skills · 23 hooks (39 handlers) · every SKILL.md carries a Fable contract footer·
v6.3.0
stable · 2026-07-02 · Orchestrator/Executor doctrine — pay for Fable on the thinking, not the typing·
/ccc-orchestrate · /ccc-handoff · /ccc-adopt — Fable/Opus plans, GPT-5.5/Sonnet executes, ~70% token savings·
70 plugin skills · printable cheat-sheet PDFs · full docs audit·
v6.2.0
stable · 2026-06-30 · Sonnet 5 support · /ccc-debate · /ccc-plan-exec · /ccc-triage·
67 plugin skills · permission/auto-mode indicators · /ccc-tuneup cost audit·
v6.1.0
stable · 2026-06-29 · 64 plugin skills · safe-YOLO setup · selective ECC loader·
workflow-first orchestration: lead session as control plane, Workflow tool and fleet do the work·
Claude Teams hard-on default via CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS·
/ccc-yolo-setup keeps Plan mode for risky changes · /ccc-ecc loads one ECC asset at a time·
64 plugin skills · 22 agents · 23 hooks (38 handlers) · core free forever · MIT licensed·
v6.0.0
stable · 2026-06-10 · Claude Fable 5 selective deep-mode · smart model routing · savings counter·
Opus 4.8 everyday default · Fable 5 escalation tier for deep reasoning · once-per-day smart nudge·
complexity-scored auto-routing across Haiku/Sonnet/Opus/Fable for subagents · ccc --savings estimate·
4 deep personas (architect · debugger · security-auditor · product-manager) now run Claude Fable 5·
v5.1.2
stable · 2026-06-05 · 62 plugin skills, 22 agents, 23 hooks, Opus 4.8 + dynamic workflows·
18 vendor submodules · /ccc-tuneup local-setup optimizer · notebooklm-py removed (AGPL)·
/ccc-ultracode — xhigh effort + auto-workflow orchestration · requires Claude Code v2.1.154+·
23 lifecycle hooks (38 handlers) · 457 skills across 11 CCC domains·
core free forever · MIT licensed · one install, zero config·
v5.1.0
Opus 4.8 session default · dynamic workflows (ccc-audit, ccc-deep-review, ccc-migrate, ccc-fleet)·
hooks expanded 9→23 events · all 18 vendor pins refreshed·
62 plugin skills · SessionStart orchestrator · clickability AskUserQuestion enforcement·
Master Claude Code instantly. 82 plugin skills. 467 ecosystem skills. 549 total skills. 22 agents. 23 lifecycle hooks x 44 handlers. 19 vendors. One install, zero config, core free forever.
You have product velocity to protect. Commander gives your team a shared methodology, severity-rated reviews, and parallel worktrees so two engineers don't redo the same plan.
The fleet-worker dispatches on git worktrees so each project stays clean. Commander remembers each client's CLAUDE.md, conventions, and review rubric — context-switching becomes a slash command.
You don't need a project manager. You need 22 of them, on tap. Commander ships the discipline that solo devs end up reinventing on year three of a project.
Hooks log every tool use. PreToolUse blocks unknown commands. The security-auditor flags SEV-1 before deploy. MIT licensed, self-hosted, opt-out anonymous telemetry — pass the SOC2 review on the first try.
Stock Claude Code is a blank terminal with amnesia. Every other plugin solves one slice. Commander is the first guided AI PM — click-first UX, an intelligence layer that thinks before you do, and the whole ecosystem pre-wired.
81 click-first /ccc-* slash commands. Every menu is a native chip picker — no typing, no YAML, no syntax to memorize.
22 specialist sub-agents with persona voices — architect, reviewer, security-auditor, debugger, designer. Workflow-first orchestration keeps the lead session as the control plane while the Workflow tool and fleet do substantive work.
23 lifecycle hooks x 44 handlers. SessionStart through SubagentStop fire automatically — the right agent runs at the right moment, every time.
An 11-agent, adversarially-verified audit swept every subsystem, and every confirmed finding shipped. The compaction error is gone: every /compact used to trigger “Hook JSON output validation failed” because the PostCompact hook emitted output Claude Code's validator rejects — the emit layer now guards the validator's real 20-event union (extracted from the CLI binary itself) and the contract test drives every emitter under its real registered events, so this bug class can't ship green again. Mission Control finally tells the truth: finished subagents used to stay “working” forever (78 of 3,337 telemetry rows ever joined) — the roster now joins on agent_id. Keyless everywhere: every shipped surface — MCP guide, Cursor/Windsurf adapters, config templates — now says the same thing: free hosted MCP, no account, no license key, 100-call/mo anti-abuse cap. Plus: the rtk vendor picked up six upstream security fixes, root npm audit is 0, /ccc-connect captures credentials via a hidden-input terminal command (never chat), /ccc-tuneup is reachable by chips, and all 11 domain routers open a picker on bare invocation.
Every Commander artifact now shares a Commander decks switcher, so you can jump between the Cockpit, Mission Control, Usage & Cost, and Safety without leaving the page. Two new decks join the family this release. Usage & Cost (/ccc-usage) is a self-contained artifact showing what your agent work actually costs and what delegating to cheaper models saved you — an honest savings estimate, saved-per-day and cost-per-day trends, and a cost-by-app breakdown. Safety (/ccc-safety) shows what Commander's hooks caught for you: dangerous actions blocked, auto-fixes applied, actions approved, and a redacted tool-failure hotspot list — no raw command output, no secrets, just outcomes.
The Cockpit — every Commander tool inside one self-contained artifact — got a real redesign on the commanderplugin.com coral brand. Browse is now a filterable skill list with a rows/tiles toggle and real-time search, instead of a wall of one-skill "domains" — a clean 14-domain taxonomy, no misleading "core". Enhance turns 11 prompt-improvement strategies into multi-select chips with a GO that appends exactly the ones you pick. And the telemetry is honest now: real per-agent token and cost numbers, recovered from each subagent's own transcript (deduped so streaming turns aren't double-counted, cache reads priced in) — or a plain "—" when the data was never captured, never a fabricated zero. New in this release: a Tools tab that turns the Cockpit into an ecosystem launcher — open Commander surfaces, install the best MIT-licensed companion apps (Nimbalyst, Usage Monitor, Sniffly, Claude Control), or copy a prompt that has Claude build a live dashboard.
Mission Control's Claude+Codex rosters now come with the receipts. A zero-dependency Charts strip — inline SVG, one shared module rendering both the live dashboard and the CSP-safe snapshot artifact — plots cost/day, agents dispatched/day, tasks completed/week, and tool failures/day, theme-safe with a clean zero-state instead of a broken axis. A new claude-mem History panel adds a read-only, titles-only timeline over your claude-mem DB (opt-in — hidden entirely when claude-mem isn't installed). And the Agent Roster is finally complete: Codex Desktop's hook surface drops several events CCC relies on for real start records, so Codex work showed up in the Live Feed but never the roster — now those rows are synthesized from delegation events, marked "inferred" with a dimmed badge and tooltip, and never claim token/cost data that isn't real. All backed by a metrics.jsonl daily rollup (ccusage-sourced, Claude + Codex) and a per-skill Claude/Codex breakdown, with a TTL cache so the dashboard scales with more concurrent viewers.
Every Commander tool, clickable, inside one artifact. Published from /ccc-browse → "🎛️ Open the Commander Cockpit": a self-contained, CSP-safe page with five tabs — Browse (78 plugin + 467 ecosystem skills, 22 agents, instant search, job-first row, copy-to-run), Ideas (catalog-grounded next-move generator), Enhance a prompt (six prompt-quality patterns as a live checklist), Analytics (your own agent runs — tokens, cost, 14-day sparkline, top agents, Claude and Codex side by side via source_app), and Agents (roster manager — edit a profile in-page, export it). A new skill-runs logger (the 42nd hook handler) records which skills you actually launch, powering Cockpit's per-skill analytics.
A visual harness inside Claude Code Desktop — see who's working on what, delegation and data flow, plain-English status of every agent, built for non-coders managing coding agents. /ccc-mission-control opens a live dashboard (agent roster, delegation flow graph, task board, live event feed, an amber awaiting-permission state so unattended fleets never stall silently) or a snapshot artifact you can check from your phone. v6.8.1 added multi-source tracking — agents and events tagged by source app (Claude vs Codex) with a Source filter and colored pill — plus a Suggestions panel for proactive ideas you can promote straight to a Linear ticket.
Five new skills across the v6.7.x line. /ccc-relay chains independent, gated spec → build → review sessions with a durable handoff baton (merge stays human-approved). ccc-smb-ops adds a small-business-operations domain (invoicing/AR, cash-flow, payroll, CRM, weekly owner brief). /ccc-broadcast pushes scrubbed build/deploy/CI/cost status to your team's chat or email. /ccc-spawn is a click-first spawn hub — a spawn_task chip in Cowork, /spawn in the CLI. And /ccc-prompt-fix — the auto prompt fixer — diagnoses your prompt against six quality patterns and hands back a tighter rewrite, backed by the integrated claude-code-library (52 Claude Code prompts + a 7-module best-practices course).
Hook delivery rebuilt on the documented output fields (systemMessage / hookSpecificOutput.additionalContext) so recommendations actually reach the model and the user, not just stdout. Always-on skill suggestions now surface as clickable AskUserQuestion chips once confidence is high, instead of printed text you have to notice. /ccc-claudemd — the new CLAUDE.md auto-auditor — is the 72nd plugin skill. Verifier-separation and mandatory git-worktree isolation now cover every write path (ccc-migrate, ccc-orchestrate, ccc-plan-exec, ccc-fleet).
The operating doctrine distilled from Claude Fable 5, encoded as 12 enforceable gates — never trust a single pass · loops need verifiers, state, and stops · prove before you alarm · context is disposable, state is durable · orchestrate, don't type — so ANY model running CCC, Sonnet, GPT, anything, produces Fable-shaped results. /ccc-fable is the master switch: on arms the doctrine, status reports what's armed, audit self-checks which gates the session is violating, off disarms. Every one of the 71 skills carries a Fable-contract footer enforced by an audit test.
/ccc-yolo-setup turns on vetted safe-YOLO while keeping Plan mode for risky changes. /ccc-ecc selectively loads one ECC skill, agent, or hook without duplicating the full harness. Claude Teams is a hard-on default.
Opus 4.8 everyday default. Claude Fable 5 selective deep-mode escalates 4 deep personas (architect · debugger · security-auditor · product-manager) for heavy reasoning — a once-per-day nudge tells you when it pays off. Complexity-scored auto-routing across Haiku/Sonnet/Opus/Fable for subagents keeps costs honest. ccc --savings shows an estimated spend vs an all-Opus baseline (±30%).
/ccc and watch the orchestrator dispatch.Three surfaces, one plugin. Pick a chip on the left — the brain routes to the right specialist, hooks fire on lifecycle events, hands ship the diff.
/ccc-saas. Pick a workflow:stripe-checkoutbuilder + saas-specialistPreToolUse — verifying scope, deps, secretsScaffolded /api/checkout, wired client SDK, added webhook handler. Ready for review.
3 SEV-2 findings on session rotation. Suggested patches attached. /ccc-review --apply
FOR/AGAINST analysis on the email provider choice. Resend vs Postmark vs SES. ETA 2m.
From cold-start to /ccc in under 30 seconds. No API keys, no signup, no credit card. The plugin marketplace handles the rest.
Stock Claude Code is a blank prompt. You write the methodology, the spec template, the review rubric, the hook handlers. Or you type one slash command.
# CLAUDE.md ## Persona You are a senior engineer working on a SaaS product. You plan first, ship small, and operationalize fixes. ## Workflow for new features 1. Spec interview: ask 5-7 clarifying questions before code. 2. Write a plan.md with: scope, schema, files touched, tests. 3. Wait for approval before any implementation. 4. Implement in vertical slices, one PR at a time. 5. Run reviewer pass: severity-rate every diff. ## Review rubric SEV-1 = blocks deploy (auth, payments, data loss) SEV-2 = must fix before merge (race, perf, regression) SEV-3 = should fix this sprint (polish, dx) ## File conventions - src/* uses TypeScript strict mode - API routes return Result<T, AppError> - Webhooks verify signatures, no exceptions - Migrations are reversible - New deps require one-line justification ## Hooks - Before any tool use, log to .claude/audit.log - After session end, summarize diffs in NOTES.md - On error, dispatch debugger sub-agent - ... (180 more lines)
$ /plugin install commander ✓ 81 skills active ✓ 22 agents wired ✓ 23 hooks × 44 handlers ✓ BIBLE.md methodology loaded ✓ review rubric: SEV-1/2/3 # now type: $ /ccc-plan add stripe checkout → commander interviews you (5 questions) → writes plan.md → waits for approval → dispatches builder + saas-specialist → reviewer passes severity check → ships # the methodology is already written. # the agents are already wired. # the hooks are already firing. # you just type slash commands.
Stock Claude Code ships a powerful blank canvas. Commander adds the workflow layer most teams end up rebuilding from scratch — except it’s already built, opinionated, and free.
/ccc-suggest recommends by nameEach agent embodies a distinct role, model and voice — wired through the Claude Agent SDK sub-agent architecture. Ask once; the right specialist runs every time.
Every plugin skill that ships with Commander. Filter by domain, click a card to peek at the YAML manifest. The agent doesn't pick by accident — it picks from this menu.
Domain routers narrow the 467-skill ecosystem down to the half-dozen moves that matter for what you’re doing right now. Type the slash command, click the chip.
Every Claude Code event has a handler attached. Hover the timeline to see what fires when, and which handlers ship by default.
A two-layer SDK pattern with lifecycle automation between. Skills become inputs, agents become tools, hooks become guardrails. You write nothing — it’s already wired.
“Plan first. Ship small.
Operationalize fixes.”
Every feature starts with a spec interview. /ccc-plan writes a plan file you can read, review and reject before a token is burned on implementation.
The reviewer agent enforces it. Diffs that try to do two things get rejected with a severity rating. Boring is the strategy.
Every regression that lands in production turns into a lifecycle hook. The session never has to remember — it’s already enforced.
Every skill, every agent, every hook, every domain router — installable today, in beta, in production, on day one thousand. MIT licensed. It will not get worse.
/ccc-connect (you see them, you choose) and Kevin Z’s consulting practice underneath. The plugin itself is, and stays, MIT.
Works in Claude Code Desktop, the CLI, and any MCP-capable IDE. Pick the path that matches where you live — same plugin underneath.
Settings → Plugin Marketplace → Add from GitHub. Or run it from the CLI.
$/plugin marketplace add KevinZai/commander
One command activates 82 plugin skills, 467 ecosystem skills, 22 agents, 23 lifecycle hooks x 44 handlers, and 19 vendors.
$/plugin install commander
/ccc.The chip picker pops. Build · Review · Ship · Design · Learn · More. Click and go.
$/ccc
/ccc-connect shows transparent affiliate links to optional MCP integrations (Supabase, Vercel, Notion, etc.) — you see them and choose. Kevin Z’s consulting practice covers the rest.context7 and sequential-thinking — are credential-free. Sixteen optional integrations are opt-in via /ccc-connect; only those need keys, and only if you want them.mcp.commanderplugin.com — same 467 ecosystem skills across 11 domains, one URL./ccc-plan, /ccc-review). An agent is a persona with a distinct role, model, and voice that the orchestrator dispatches to. Skills route to agents. The brain/hands pattern./ccc-suggest recommends specific third-party plugins by name when they’re the right tool — claude-mem for persistent memory, superpowers for structured thinking, caveman for token-heavy iteration, and a dozen more./plugin uninstall commander removes everything. Or for the binary install, ./uninstall.sh at the repo root. No background daemons, no system-wide configs, nothing left behind.CCC_TELEMETRY=0 or ~/.commander/config.json → {"telemetry": false}. The hosted MCP endpoint logs tool name, latency, and call count for rate-limiting (100 calls/mo free tier) but never logs prompt content or Claude's responses. This site uses Plausible (cookieless) + PostHog (first-party cookie) for pageview and click analytics — no session replay, no third-party trackers. Full breakdown in our privacy policy. Self-host the MCP server to keep everything on your box.KevinZai/commander, or DM @commanderplugin on X. Or just run /ccc-doctor — if it’s a known regression, it’ll tell you the workaround. Otherwise it generates a bug report ready to paste.$/plugin install commander