Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/kevinzai/commander/ccc-mission-control)<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-mission-control"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-mission-control.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00022 | $0.02737 |
| Opus 5 | $0.00011 | $0.01368 |
| Sonnet 5 | $0.00004 | $0.00547 |
| Haiku 4.5 | $0.00002 | $0.00274 |
Grade A, and why
ccc-mission-control scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:4690/ How it starts
The opening of the file, as written. The whole thing — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-mission-control — Mission Control
One board that answers "who's working on what?" without reading a single log line. Every CC Commander session already journals its agent runs, tasks, and delegations to ~/.claude/commander/ (subagent-runs.jsonl, agent-runs.jsonl, tasks.jsonl, mission-control/events.jsonl). Mission control turns those logs into a picture a non-coder can read: agent roster, task board, delegation flow, and a plain-English summary.
🔒 Privacy: everything runs locally by default — the live dashboard binds to 127.0.0.1 and no data leaves your machine. The one exception is the optional 📤 snapshot artifact: publishing uploads the snapshot (agent names, task subjects, timings) to your private claude.ai artifact URL — it starts private to your account, but treat it as leaving the machine. The skill always asks before publishing, and never publishes automatically.
How it routes
On $ccc-mission-control with no argument, open a click-first picker:
AskUserQuestion:
question: "Mission control — how do you want to see your agents?"
options:
- 🖥️ Open live dashboard — auto-refreshing panel that sits beside your chat
- 🛰️ Publish snapshot artifact — a living status page you can keep or share
- 🗣️ Plain-English status — narrate it right here, zero jargon
- 💡 Review & promote suggestions — triage the ideas agents have surfaced
- ⏹️ Stop dashboard — shut the local server down
Explicit sub-commands skip the picker: $ccc-mission-control open, $ccc-mission-control snapshot, $ccc-mission-control status, $ccc-mission-control suggestions, $ccc-mission-control stop.
Zero-state: if the logs are empty or missing, say so plainly and point forward — "No agents yet — spawn one with $ccc-spawn (or fan out with $ccc-fleet) and this board lights up." Never render an error for an empty board.
🖥️ Open live dashboard ("sits on the left side" mode)
- Check whether the dashboard is already up:
curl -s -o /dev/null -w '%{http_code}' http://127.0.0.1:4690/ - If not
200, start it — runnode dashboard/server.jsas a background task from the CC Commander repo root. Finding that root:- Working inside the CCC repo → use the current checkout.
- Installed via marketplace → the plugin lives in the marketplace cache; the repo checkout is at
${CLAUDE_PLUGIN_ROOT}/../..— verifydashboard/server.jsexists there before launching. - No
dashboard/server.jsanywhere → fall back to snapshot mode (next section) instead of failing.
- Open the Browser pane at
http://127.0.0.1:4690/mission-control.html(preview_start {url}). The panel docks beside the chat and keeps itself fresh while you keep working.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 176 lines · 22 tokens per session scan A a52b2a2f7067
ccc-mission-control is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 2,737 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
debt-ops-add
Register a deferred decision in the tech-debt registry. Trigger by judgment, not a marker scan, whenever a future reader would ask "why this way?": an unmade decision, stub, loosened type, bypassed check, swallowed error, a default picked "for now", or a TODO/FIXME/HACK/XXX marker. Trigger immediately whenever you…
import
Import a tasks.md into the coco tracker as an epic with dependencies, and create matching issues in the configured issue tracker.
hotfix
Single-issue workflow for quick fixes and small changes that don't need full epic tracking. Creates a branch, implements the fix, commits with issue tracking, and closes.
debt-ops-review
Audit the tech-debt registry, rank survivors by churn × Fowler quadrant, surface a top-N list, then walk paydown on user follow-up. Use when the user asks to review debt, see what to pay down, work through entries, or check the debt registry. Stale entries drop with "drop A,B,C".
loki-mode
Multi-agent autonomous startup system for Claude Code. Triggers on "Loki Mode". Orchestrates 100+ specialized agents across engineering, QA, DevOps, security, data/ML, business operations, marketing, HR, and customer success. Takes PRD to fully deployed, revenue-generating product with zero human intervention.…
moai-workflow-project
Integrated project management system covering documentation, language initialization, template optimization, docs generation, and JIT document loading. Absorbed from moai-workflow-templates, moai-docs-generation, and moai-workflow-jit-docs.