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-devopsgit 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-devops)<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-devops"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-devops/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-devops"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-devops.svg" alt="Reviewed on agentmods" width="80" 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.00067 | $0.01345 |
| Opus 5.5 | $0.00027 | $0.00538 |
| Sonnet 5.5 | $0.00013 | $0.00269 |
| Haiku 4.5 | $0.00007 | $0.00135 |
Grade A, and why
ccc-devops 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-devops — route to the DevOps specialist
CC Commander · $ccc-devops · one entry point that loads the matching DevOps specialist playbook for the task.
The specialist list, routing matrix and multi-step campaigns live in references/routing.md. The user's selected model is preserved; the only delegation is the optional devops-engineer agent in step 4.
Codex: ask the pickers as plain-text questions; run step 4 with codex exec --json using the specialist playbook as the instructions.
When to use / when not to
- Use to design or change a pipeline, deploy strategy, container image, cloud architecture, IaC module, monitoring stack, network layout or incident runbook.
- Not for: a red CI run right now (
$ccc-ci), running an actual deploy ($ccc-deploy), pre-launch account hardening across Vercel/GitHub/Cloudflare ($ccc-harden), or local service status ($ccc-infra).
What happens
-
Map the intent. Match
$ARGUMENTSor the user's words against the routing matrix in references/routing.md. A multi-step goal ("set up monitoring end to end", "build our AWS stack") maps to a campaign in references/routing.md. No clear intent: ask the domain picker (Decision points). -
Confirm constraints before infrastructure work. Read what the repo already uses, then confirm cloud provider, toolchain and environment with the user only where the files do not answer it:
ls -d .github/workflows Dockerfile docker-compose*.yml *.tf terraform k8s helm fly.toml vercel.json serverless.yml cdk.json 2>/dev/null -
Load the specialist. Glob for
**/skills/ccc-devops/<specialist>/SKILL.md(in the Commander repository it isskills/ccc-devops/<specialist>/SKILL.md; in an installed CLI toolkit it sits under the toolkit'sskills/directory) and Read it. Follow that playbook for the task. If no match exists, work from the specialist's one-line scope in references/routing.md and say the full playbook is not installed. For a campaign, load each specialist in order and finish one step before the next.
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 Changed · -13 lines · +29 tokens per session 36a3ae047b0d
- 1mo ago First seen · 98 lines · 38 tokens per session scan A fc9565c81ba6
ccc-devops is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 1,345 once invoked, about $0.0003 per session on Opus 5.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
relay-deploy
Set up a complete deployment configuration — Dockerfile, deployment manifest, environment config, and rollback procedure. Use when asked about "deployment setup", "how do I deploy this", "deployment strategy", or "rollback plan".
devops
Comprehensive DevOps engineering practices for Kubernetes, CI/CD, Bash scripting, Ansible, and cloud infrastructure.
relay-docker
Build production-ready Dockerfiles with multi-stage builds, security hardening, and docker-compose for local dev. Use when asked to "create Dockerfile", "optimize container", or "dockerize this".
infra-standards
Infrastructure, container, and CI/CD discipline — IaC, Dockerfiles and compose files, CI pipelines, platform deploy config, env/secrets handling. INVOKE PROACTIVELY when creating or editing any such file (.tf, .bicep, Dockerfile, docker-compose, .github/workflows/, vercel.json) — even when nobody says "infra". Not for…
devops
DevOps patterns: containerization, CI/CD, deployment strategies, monitoring. Use when containerizing apps, setting up pipelines, or deploying services.
devops-patterns
DevOps patterns for infrastructure, CI/CD, and deployment automation. Use when configuring Docker containers, CI/CD pipelines, cloud deployments, Kubernetes, and monitoring. Covers GitHub Actions, Docker, Vercel, Railway, AWS, Terraform, and observability.