[skills]plugin/commander
Skills
64 click-first /ccc-* slash commands. Every menu is a native chip picker — no typing, no YAML, no syntax to memorize.
13 specialist workflows
14 domain routers
CC Commander — Master Claude Code instantly. Free for now.
Master Claude Code instantly. 64 plugin skills. 22 specialist agents. 23 lifecycle hooks. One install, zero config, free for now.
› try a real command — claude responds in this box
$
runs in
Same plugin, every editor.
12 surfaces · MCP under the hoodClaude Code Desktopnative
Claude Code CLInative
Claude Coworkbeta
Cursorvia MCP
Windsurfvia MCP
OpenAI Codexvia MCP
VS Codevia MCP
JetBrainsvia MCP
Zedvia MCP
Continuevia MCP
Clinevia MCP
+ MCP clients7 more
tailored to you
Who's shipping?
Ship features without rebuilding the workflow.
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.
Run 4 client projects in parallel without dropping the rope.
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.
One person. Full team output.
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.
The audit trail your security team has been asking for.
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.
why CC commander
Claude Code is powerful. CCC makes it instantly usable.
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.
[agents]plugin/commander
Agents
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.
22 personas
brain/hands SDK
[hooks]plugin/commander
Hooks
23 lifecycle hooks × 38 handlers. SessionStart through SubagentStop fire automatically — the right agent runs at the right moment, every time.
23 hooks
38 handlers
[v6.1.0]plugin/commander
Safe delegation
/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.
safe-YOLO · Plan mode
ECC selective load
see it live
Click
Click /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.
you
add stripe checkout to the pricing pagecommander
I'll route this through /ccc-saas. Pick a workflow:$/ccc-saas71 skills · pick one
brain orchestrator picked
stripe-checkouthands dispatching →
builder + saas-specialisthook
PreToolUse — verifying scope, deps, secretsbuilder · #142 stripe checkout
Scaffolded /api/checkout, wired client SDK, added webhook handler. Ready for review.
reviewer · #143 auth refactor
3 SEV-2 findings on session rotation. Suggested patches attached. /ccc-review --apply
fleet-worker · 4 worktrees in flight
FOR/AGAINST analysis on the email provider choice. Resend vs Postmark vs SES. ETA 2m.
$ /ccc
┌─ commander ─────────────────────────────────────────────┐
│ pick a workflow
│
│ [1] /ccc-plan spec interview → plan.md
│ [2] /ccc-build scaffold and ship
│ [3] /ccc-review severity-rated diff review
│ [4] /ccc-fleet parallel git-worktree dispatch
│ [5] /ccc-doctor diagnose · fix · report
└─────────────────────────────────────────────────────────┘
› choose [1-5]: 3
✓ dispatching reviewer agent
✓ hook PreToolUse fired
scanning diff: 14 files · 312 lines
⚠ SEV-2 · src/auth/session.ts:84
session rotation missing on privilege escalation
⚠ SEV-3 · api/checkout.ts:21
stripe webhook signature not verified
› apply patches? y
✓ 2 patches written, hook PostToolUse green
install demo
One command. Whole ecosystem online.
From cold-start to /ccc in under 30 seconds. No API keys, no signup, no credit card. The plugin marketplace handles the rest.
200 lines vs one slash
The plan you'd write. The plan it writes.
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.
stock claude code~200 lines · CLAUDE.md
# 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)
+ commander1 line · zero config
$ /plugin install commander ✓ 64 skills active ✓ 22 agents wired ✓ 23 hooks × 38 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 vs commander
The same Claude Code. A different machine.
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.
capability
stock claude code
+ commander
Slash-command workflows
none built-in
64 skills, click-first picker
Specialist sub-agents
roll your own
22 wired personas, day one
Lifecycle hooks
config required
23 hooks × 38 handlers, on by default
Plugin discovery
manual
/ccc-suggest recommends by nameParallel work
single thread
git-worktree fleet, FOR/AGAINST runs
Persistent methodology
your CLAUDE.md
BIBLE.md + the Kevin Z method
Cost
free
also free, MIT, forever
22 specialist agents
Brain orchestrates. Hands ship.
Each 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.
architect
Designs system shape and constraints before a line is written.
reviewer
Severity-rated code review on the current diff or branch.
builder
Scaffolds projects, generates code, executes the plan.
debugger
Reproduces, isolates, patches — never guesses past a stack trace.
security-auditor
Path traversal, cwd validation, dependency vuln triage.
performance-eng
Profiles, benchmarks, trims the bottleneck path.
designer
UI/UX flows, component design, Figma-to-code.
product-manager
Spec interviews, plan files, scope discipline.
technical-writer
Docs, READMEs and changelogs that read like a person wrote them.
content-strategist
Marketing, launch posts, narrative shape for releases.
data-analyst
SQL, dashboards, ad-hoc data spelunking with citations.
devops-engineer
CI, deploys, infra-as-code, rollback playbooks.
qa-engineer
E2E suites, Playwright automation, visual regression.
researcher
Surveys the field; returns options with trade-offs, not opinions.
fleet-worker
Parallel git-worktree runs — fan-out, pipeline, FOR/AGAINST.
typescript-reviewer
Strict types, generics, narrowing, exhaustive checks.
python-reviewer
Type hints, ruff, async patterns, packaging hygiene.
all 64 skills
Browse the index.
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.
showing 64 of 64
11 CCC domains
Every workflow has a domain.
Domain routers narrow the 457-skill ecosystem down to the half-dozen moves that matter for what you’re doing right now. Type the slash command, click the chip.
$ls -lh ./domains
total 11
drwxr-xr-x62 skillsmay 06/ccc-designUI · UXlanding · components
drwxr-xr-x71 skillsmay 06/ccc-saasappsstripe · auth · email
drwxr-xr-x54 skillsmay 05/ccc-devopsinfraci · deploy · rollback
drwxr-xr-x48 skillsmay 05/ccc-marketinggrowthlaunch · copy · ads
drwxr-xr-x42 skillsmay 04/ccc-dataSQL · BIdashboards · pipelines
drwxr-xr-x38 skillsmay 04/ccc-testingQAe2e · unit · visual
drwxr-xr-x33 skillsmay 03/ccc-securityauditvuln · authn · authz
drwxr-xr-x31 skillsmay 03/ccc-mobileiOS · Androidexpo · react-native
drwxr-xr-x29 skillsmay 02/ccc-seogrowthschema · sitemap
drwxr-xr-x26 skillsmay 02/ccc-researchreconsurvey · trade-offs
drwxr-xr-x23 skillsmay 01/ccc-makeoverrefactorUI polish · dx
457 total skills · click any domain to browse the catalog
23 hooks · 38 handlers
Lifecycle, automated.
Every Claude Code event has a handler attached. Hover the timeline to see what fires when, and which handlers ship by default.
architecture
Brain orchestrates. Hooks fire. Hands ship.
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.
1. input
/ccc
/ccc-plan
/ccc-review
/ccc-yolo-setup
/ccc-ecc
+ 58 more
↓ 64 skills
2. brain
control plane
workflow-first router
plan-file writer
scope guard
↓ dispatch
3. hands
architect
builder
reviewer
debugger
security-auditor
+ 12 more
↓ lifecycle
4. hooks
SessionStart
PreToolUse
PostToolUse
UserPromptSubmit
SubagentStop
+ 4 more
the Kevin Z method
“Plan first. Ship small.
Operationalize fixes.”
01 — plan first
Spec before code.
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.
02 — ship small
One commit, one idea.
The reviewer agent enforces it. Diffs that try to do two things get rejected with a severity rating. Boring is the strategy.
03 — operationalize fixes
A bug becomes a hook.
Every regression that lands in production turns into a lifecycle hook. The session never has to remember — it’s already enforced.
free for now
No paywall. No feature gating.
No paywall. No feature gating.
No license checks.
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.
How it stays free: transparent affiliate links inside
/ccc-connect (you see them, you choose) and Kevin Z’s consulting practice underneath. The plugin itself is, and stays, MIT.
quick start · 30 seconds
Three steps. You’re live.
Works in Claude Code Desktop, the CLI, and any MCP-capable IDE. Pick the path that matches where you live — same plugin underneath.
01 — add the marketplace
Point Claude Code at the repo.
Settings → Plugin Marketplace → Add from GitHub. Or run it from the CLI.
$/plugin marketplace add KevinZai/commander
02 — install commander
Pull the plugin.
One command activates 64 skills, 22 agents, 23 hooks, and 2 MCP servers.
$/plugin install commander
03 — start commanding
Type /ccc.
The chip picker pops. Build · Review · Ship · Design · Learn · More. Click and go.
$/ccc
faq
Questions, answered.
Is this really free? What’s the catch?
Yes — MIT licensed, free for now. The plugin itself never gates features.
/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.Do I need an API key or signup?
No. The two bundled MCP servers —
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.Does it work outside Claude Code?
Yes. Native plugin install in Claude Code Desktop and the CLI. For Cursor, Windsurf, Cline, Continue, and Codex, point the MCP client at
mcp.commanderplugin.com — same 457 skills across 11 domains, one URL.What’s the difference between a skill and an agent?
A skill is a slash command — a workflow you invoke (
/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.How does it interact with other plugins?
Commander is a meta-layer, not a walled garden.
/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.Can I uninstall cleanly?
Yes —
/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.What about privacy and telemetry?
The plugin collects anonymous usage telemetry (enabled by default, easy to opt out). It sends event names, OS, Node version, and plugin version — never prompts, file contents, paths, or secrets. Opt out with
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.How do I report a bug or request a skill?
GitHub issues at
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.support cc commander
Keep it free. Stay in the loop.
Star on GitHub
The fastest way to help. Stars signal traction and bring CC Commander to more developers.
Sponsor on GitHub
Help keep CC Commander free. Recurring or one-time — every dollar funds the hosted MCP infrastructure.
Custom Claude Code Consulting
$1k–10k engagements for teams adopting Claude Code at scale. Architecture, onboarding, and agent workflows.