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 skills add KevinZai/commander --skill ccc-spawngit 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-spawn)<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-spawn"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-spawn.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.00048 | $0.01091 |
| Opus 5 | $0.00024 | $0.00545 |
| Sonnet 5 | $0.00010 | $0.00218 |
| Haiku 4.5 | $0.00005 | $0.00109 |
Grade A, and why
ccc-spawn 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-spawn — Spawn Hub
Spin work off into its own session on demand — the manual counterpart to the automatic isolation-spawn nudge (suggest-ticker). One click-first entry point that routes to the right spawn mechanism for what you're doing, and for the surface you're on.
Surface-aware. In Claude Cowork Desktop, spawning a one-off session is a
spawn_tasksidebar chip. In the Claude Code CLI, it's a/spawnpeer via the claude-peers broker. This skill picks the right one automatically — you don't have to know which surface you're on.
When you'd reach for it
- "This is a separate, self-contained thing — do it in its own session so it doesn't derail here."
- "Fan this out across N files in parallel."
- "Run spec → build → review as a chain of hand-off sessions."
- "Get a fresh, independent expert pass on this."
How it routes
On $ccc-spawn with no argument, open a click-first picker:
AskUserQuestion:
question: "What do you want to spawn?"
options:
- Isolated session — one self-contained task, its own fresh context
- Parallel fleet — fan out across independent files/units at once
- Cross-session relay — chain spec → build → review as hand-off sessions
- Expert pass — one independent reviewer (security / perf / design / …)
| Choice | Surface behaviour | Under the hood |
|---|---|---|
| Isolated session | Cowork → emit a spawn_task chip [⭐ Spawn as separate session]; CLI → /spawn quick <task> |
A fresh peer/session with a self-contained brief; never derails the current thread |
| Parallel fleet | Route to $ccc-fleet (worktree-isolated parallel agents) |
fan-out / pipeline / judge / debate modes |
| Cross-session relay | Route to $ccc-relay |
loop-state hand-off, spec→build→review→merge |
| Expert pass | Cowork → spawn_task chip scoped to one reviewer persona; CLI → /spawn expert <domain> |
a single fresh-context reviewer, prompted to refute (Pillar 2) |
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 · 81 lines · 48 tokens per session scan A 1fad76e2560f
ccc-spawn is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 1,091 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-09-03.
Other skills, from other repositories
prompt-library
Curated collection of high-quality prompts for various use cases. Includes role-based prompts, task-specific templates, and prompt refinement techniques. Use when user needs prompt templates, role-play prompts, or ready-to-use prompt examples for coding, writing, analysis, or creative tasks.
memstack-automation-n8n-workflow-builder
Use this skill when the user says 'n8n workflow', 'build a workflow', 'automation workflow', 'connect services', or needs visual workflow design with node mapping, data transformations, and error handling for n8n. Do NOT use for standalone webhook endpoints or cron jobs.
cco-clean
Clean up old tracking data and reset statistics.
search-first
A workflow rule for searching for an existing solution before writing new code. It checks the repository, internal mirrors, package registries, connected tools, and GitHub in that order.
multi-plan-handoff
Auto-detect plan files in conversation context and pass them to multi: execute subagents by reference, not by paraphrase.
command-dev
Use this skill when creating or refining custom Claude Code slash commands. Slash commands are user-invoked reusable prompts that can accept arguments, reference files, and execute bash operations. Helps design command syntax, argument handling, file references, bash execution, and frontmatter configuration.…