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-shipnpx skills add KevinZai/commander --skill ccc-shipgit 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-ship)<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-ship"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-ship.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.00038 | $0.02595 |
| Opus 5 | $0.00019 | $0.01298 |
| Sonnet 5 | $0.00008 | $0.00519 |
| Haiku 4.5 | $0.00004 | $0.00260 |
Grade A, and why
ccc-ship 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 yesterday.
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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-ship — Pre-flight + deploy
Click-first ship flow. Four actions, one test matrix, one release pipeline, one deploy path. User picks the action, the matrix (or agent) runs, results surface as a checkbox scorecard.
Session markers
Call mcp__ccd_session__mark_chapter at these phase transitions:
| Trigger | title | summary |
|---|---|---|
| User picks "Pre-flight check" (before matrix runs) | "Ship preflight: <branch>" |
"Running preflight matrix on <branch>" |
| After test matrix completes | "Tests: <pass>/<total>" |
"<pass>/<total> tests passing; <N> gates remaining" |
| All gates evaluated, before presenting verdict | "Preflight complete" |
`"Verdict: <GO |
| After release tag is pushed | "Release tagged <version>" |
"v<version> tagged and pushed to GitHub" |
Sidebar chips (spawn_task)
After the preflight verdict, IF any gate fails (tests red, security findings, build fail, unclean diff), spawn ONE mcp__ccd_session__spawn_task chip per failure:
title: actionable imperative under 60 chars (e.g.,"Fix 3 failing tests before ship"or"Resolve doc-sync: README still references v3.2.0")prompt: self-contained — include the exact gate that failed, the error output or file:line if available, and the fix direction. The spawned session has no memory of this conversation.tldr: 1-2 sentences plain English explaining what broke and what to do.
Chips fire after the preflight scorecard is rendered — never before.
Response shape (EVERY time)
Output exactly these three sections in order:
1. Brand header (one line, markdown)
**CC Commander** · $ccc-ship · Pre-flight → tag → deploy
2. Context strip (one paragraph)
Detect ship readiness with five quick reads (parallel Bash, silent on failure):
git rev-parse --abbrev-ref HEAD→ branchgit status --porcelain | wc -l→ uncommitted changesgit rev-list --count main..HEAD 2>/dev/null→ commits ahead of maintest -f package.json && node -p "require('./package.json').version"→ current versiontest -f .github/workflows/ci.yml && echo yes→ CI configured
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.
- yesterday First seen · 225 lines · 38 tokens per session scan A 17e0258616e6
ccc-ship is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 2,595 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
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
ops-ship
OPS on-demand: This skill should be used when the user asks to "ship ops plugin", "merge all PRs and…
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
pipeline-digest
Daily release-pipeline digest with a change gate — reports which plugins are pending release, whether main's CI is green, and which branches went stale, and notifies the operator only when that state actually moved since the last run. Use when the operator asks "what moved in the pipeline", "anything to ship"…
ai-agents-generation-and-release
Operate the ai-agents generation and release machinery, covering the seven buildall.py generators, generateagents.py, syncpluginlib.py, the drift gates, the version-free plugin manifests, and the npm publish path. Use when you say regenerate the mirrors, run the drift checks, why is the plugin version gate red…
release
Use this agent for versioning, changelogs, release notes, deployment coordination, and release process management.