CC Commander — Master Claude Code instantly. The Fable Method: 12 enforceable gates so any model delivers Fable-shaped results. 71 plugin skills, 22 specialist agents, 23 lifecycle hooks (39 handlers). Free for now. commanderplugin.com
Show the Linear project board by status with a progress bar, pick an issue to start work on, or create a new issue, with every Linear write confirmed first. Use when you want to see or act on your Linear project from the session or the ccc CLI.
Set up a managed autonomous loop (sequential, continuous-pr, rfc-dag or infinite) with tests green first, an explicit stop condition, a runbook and a state file, then print the commands to start and monitor it. Use when preparing unattended or repeated agent work.
Report an active loop's pattern, phase, last checkpoint, iteration count, failing checks and time or cost drift, with a continue, pause or stop recommendation. Use when checking on a running or stalled autonomous loop.
Score project health with X-Ray, apply the top recommendations in impact order with your OK for each, and show the before and after score. Use when you want the highest-impact project health fixes applied and measured.
Backend-focused multi-model workflow (research, ideation, plan, execute, optimize, review) with Codex as the backend authority. Use for API design, algorithms, database work and business logic.
Multi-model collaborative execution: get a diff prototype from Codex or Gemini, refactor and apply it, then run a dual-model audit before delivery. Use to run a plan saved by /ccc-multi-plan.
Frontend-focused multi-model workflow (research, ideation, plan, execute, optimize, review) with Gemini as the UI authority. Use for components, responsive layout, UI animation and style work.
Multi-model collaborative planning: retrieve context, run Codex and Gemini analyses in parallel, and save a step-by-step implementation plan with session ids. Use before /ccc-multi-execute; plans only, never edits code.
Coordinate one change across several repositories in a single session with --add-dir: shared branch names, linked PRs, dependency-ordered merges and per-repo verification. Use for API contract changes, shared library updates and cross-service refactors.
Full multi-model development workflow with quality gates, routing frontend work to Gemini and backend work to Codex. Use for a feature that spans research through review and benefits from two model perspectives.
Stress-test a product idea before writing code through product, technical and user lenses, ending in BUILD IT, SIMPLIFY FIRST, RESEARCH MORE or KILL IT. Use when deciding whether a feature or product is worth building.
Inspect and manage an OpenClaw gateway, its agents, sessions, health and logs from a Claude Code session through the openclaw CLI. Use when you run OpenClaw and want status, agent or session operations without leaving Claude Code.
Connect CC Commander to an OpenClaw gateway: status, skill sync, configuration, health check and agent list. Use when you run OpenClaw alongside Claude Code and want the two integrated.
Run a sequential multi-agent workflow (feature, bugfix, refactor, security or custom chain) with structured handoffs, plus optional tmux and worktree workers for long-running sessions. Use when a task needs planner, implementer and reviewer stages in order.
List, search, create, comment on and close Paperclip issues from Claude Code through its REST API. Use when your team tracks agent work in a Paperclip instance.
Run several Claude Code agents at once, each in its own git worktree and branch, then merge the results through one coordinator. Use when you have independent tasks to develop concurrently.
Discover other running Claude Code instances and message them through the Claude Peers MCP server: list, send, broadcast, status, summary and inbox check. Use when several Claude Code sessions on one machine need to coordinate.
Scan a project for its frontend, backend and Python services and generate a PM2 ecosystem.config.cjs plus start, stop, restart, logs and status commands. Use when you want local dev services managed by PM2.
Analyze a draft prompt and return an optimized, copy-ready version with the matching skills, commands, agents and model tier. Advisory only: never executes the task. Use when the user wants a prompt improved before running it.
Review changed Python code for security, type safety, error handling, idioms and framework pitfalls, with static analysis results and a merge verdict. Use after editing .py files, before committing Python changes, or when reviewing a Python pull request.
Run formatter, lint and type checks on demand for a path or the whole project, then list what to fix. Use before committing, after large edits, or when the user asks for a quality gate.
Find and remove dead code one item at a time, running the test suite before and after every deletion and reverting any deletion that breaks it. Use when the user wants unused code, files or dependencies cleaned up safely.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: