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-deploynpx skills add KevinZai/commander --skill ccc-deploygit clone --depth 1 https://github.com/KevinZai/commanderWhat 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.00041 | $0.02621 |
| Opus 5 | $0.00020 | $0.01311 |
| Sonnet 5 | $0.00008 | $0.00524 |
| Haiku 4.5 | $0.00004 | $0.00262 |
Grade A, and why
ccc-deploy 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 2d 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 — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-deploy — Actual Deploy Workflow
CC Commander · $ccc-deploy · Detect target → deploy → verify → announce
Use this when the user is ready to push a build live. This is distinct from $ccc-ship and $ccc-deploy-check: $ccc-ship handles pre-flight and release tagging, $ccc-deploy-check is a readiness gate, and $ccc-deploy runs the real deploy.
Response Shape
Always return these sections:
- Brand header:
**CC Commander** · $ccc-deploy · Actual deployment
- Detection summary:
Read the repository root and report detected deploy targets from:
package.jsonscripts:deploy,deploy:prod,deploy:production,pages:deploy,wrangler:deploy,vercel:deploy,fly:deploy,publish,releasefly.toml→ Fly.iovercel.jsonor avercelpackage/script → Vercelwrangler.toml,wrangler.json, orwrangler.jsonc→ Cloudflare.github/workflows/deploy.yml,.github/workflows/deploy.yaml,.github/workflows/pages.yml, or.github/workflows/pages.yaml→ GitHub Pages or workflow deploypackage.jsonpublishConfig,bin, orfilesplus aprepublishOnlyscript → npm package publish candidate
Use parallel Bash reads where possible and keep failures non-fatal:
test -f package.json && node -e "const p=require('./package.json'); console.log(JSON.stringify({scripts:p.scripts||{}, publishConfig:p.publishConfig||null, bin:p.bin||null, files:p.files||null}, null, 2))"
test -f fly.toml && echo fly.toml
test -f vercel.json && echo vercel.json
test -f wrangler.toml && echo wrangler.toml
find .github/workflows -maxdepth 1 -type f \( -name 'deploy.yml' -o -name 'deploy.yaml' -o -name 'pages.yml' -o -name 'pages.yaml' \) 2>/dev/null
- Platform picker —
AskUserQuestion
Build the options from the detection summary, put detected targets first, and enable autocomplete for the user to override. If exactly one strong target is detected, mark that label with ⭐. Never show more than four options in a single AskUserQuestion; use the second picker below for lower-confidence targets.
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.
- 2d ago First seen · 317 lines · 41 tokens per session scan A 41bf27b2324f
ccc-deploy is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 2,621 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
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
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.
backend-builder
Используй только внутри активного Codex Project Autopilot-проекта по утверждённому плану; не включай для обычных backend-задач вне автопилота.
loongsuite-pilot-insight
基于 LoongSuite Pilot / AI Coding Agent 日志生成事件洞察、组织洞察、数据质量、研发效能和 AI Native 使用类 SLS 报表时使用；包含 AI Coding 事件表语义，以及团队报表可选的部门维表、deptuser 组织关系、指标口径和公共 CTE，通常与 sls-dashboard-builder 一起使用。.