Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/kevinzai/commander/ccc-fleetnpx skills add KevinZai/commander --skill ccc-fleetgit clone --depth 1 https://github.com/KevinZai/commanderWrote 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-fleet)<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-fleet"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-fleet.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 | $0.00044 | $0.04081 |
| Opus 5 | $0.00022 | $0.02041 |
| Sonnet 5 | $0.00009 | $0.00816 |
| Haiku 4.5 | $0.00004 | $0.00408 |
Grade A, and why
ccc-fleet scanned grade A with 0 findings 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 3d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-fleet — Parallel Agents
Launch multiple Sonnet agents in parallel worktrees. Click-first picker selects the pattern.
$ccc-fleetis the manual-dispatch sibling of the canonical workflow-first doctrine (commander/cowork-plugin/rules/workflow-first.md): same delegate-the-doing-keep-the-deciding discipline, with you explicitly choosing the fan-out / pipeline / dialectic pattern.
Promoted from commands/ccc-parallel.md (legacy slash command).
Response shape (EVERY time)
1. Brand header
**CC Commander** · Fleet Orchestrator · [Docs](https://commanderplugin.com)
2. Context strip
Detect in parallel via a single Bash call:
git worktree list | wc -l→ active worktreesgit rev-parse --abbrev-ref HEAD→ current branchsysctl -n hw.memsize 2>/dev/null \|\| free -b 2>/dev/null→ RAM (cap parallelism)
Render:
🚀 Branch:
<branch>· active worktrees · RAM: · max parallel: <3-5>
Rule: 16GB → max 3 parallel · 32GB → max 5 · 64GB+ → max 6
3. Pattern picker — AskUserQuestion
question: "Which pattern?"
header: "Fleet"
multiSelect: false
options:
- label: "🌿 Fan-out (same task × 3)"
description: "3 agents tackle different slices of one big task."
preview: "Best for: 'migrate files A-M, N-Z, update tests'."
- label: "🔗 Pipeline (sequential)"
description: "Agent 1 → Agent 2 → Agent 3, each waits on the prior."
preview: "Best for: 'design → implement → test'."
- label: "⚖️ Opposing review (FOR/AGAINST/Referee)"
description: "Dialectic — one argues FOR, one AGAINST, Referee synthesizes."
preview: "Best for: architecture decisions you'd regret reversing."
- label: "🌙 Background long-running task"
description: "One agent, backgrounded, reports back when done."
preview: "Best for: overnight scans, heavy refactors, large doc generation."
- label: "🏢 Team hierarchy (Director→Lead→Specialist)"
description: "3-tier cost-optimized: Opus plans, Sonnet builds, Haiku polishes."
preview: "Best for: large features needing architecture + implementation + polish."
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 328 lines · 44 tokens per session scan A 77025d4ec1ec
ccc-fleet is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 4,081 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
map-fast
Minimal workflow for small, low-risk changes — no planning, no learning.
airtable-webhooks
Receive and verify Airtable webhooks. Use when setting up Airtable webhook handlers, debugging X-Airtable-Content-MAC signature verification, handling the thin-ping notification, or fetching base changes (tableData, tableFields, tableMetadata add/remove/update) from the webhook payloads API.