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-cigit 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-ci)<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-ci"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-ci/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-ci"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-ci.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 4 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.02487 |
| Opus 5.5 | $0.00027 | $0.00995 |
| Sonnet 5.5 | $0.00013 | $0.00497 |
| Haiku 4.5 | $0.00007 | $0.00249 |
Grade A, and why
ccc-ci 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-ci — CI failures, diagnosed in-session
CC Commander · $ccc-ci · the failing run, its classified cause and a copy-paste fix, without leaving the session.
Pull mode (default) reads runs through the provider CLI. Push mode (init) receives HMAC-signed webhooks on a loopback receiver the user approves; its setup lives in references/webhook-receiver.md. The user's selected model is preserved; the only delegation is the optional debugger agent in step 4.
Codex: ask the pickers below as plain-text questions, and run the step 4 delegation with codex exec --json in a fresh context.
When to use / when not to
- Use when a GitHub Actions run, Vercel/Fly.io/Railway deploy or test job failed, when a production approval gate is waiting, or to follow a run until it finishes.
- Not for: writing a new pipeline (
$ccc-devops), pre-deploy readiness ($ccc-deploy-check), Commander's own install health ($ccc-doctor), or a bug with no CI context ($ccc-systematic-debugging). - Skip it for projects with no CI and fully manual deploys.
Events
| Event | Meaning | Handled in |
|---|---|---|
push |
New commit on a branch | step 2 (listed only) |
deploy_started |
Deploy job started | step 2 |
deploy_failed |
Deploy exited non-zero | step 3 |
deploy_succeeded |
Deploy completed and healthy | step 2 (duration, environment, URL) |
test_failed |
Test job reported failures | steps 3–4 |
test_succeeded |
All tests green | step 2 |
approval_required |
Manual production gate waiting | step 6 |
What happens
- Detect the provider and access.
No CI files and no provider CLI: say so and stop.ls -d .github/workflows vercel.json .vercel fly.toml railway.json railway.toml .gitlab-ci.yml 2>/dev/null command -v gh vercel fly railway 2>/dev/null gh auth status 2>&1 | head -n 3ghpresent but not authenticated: tell the user to rungh auth loginthemselves; never ask for a token. If a Vercel connector is connected, its deployment and runtime-log tools replace thevercelCLI calls below.
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.
- yesterday Changed · -1 lines d08dbe5b8f76
- 3d ago Changed · +1 lines scan B → A e98f6e2b244d
- 14d ago Changed · +2 lines · +33 tokens per session scan A → B c0f902e15ce2
- 1mo ago First seen · 151 lines · 34 tokens per session scan A 1df049c9c602
ccc-ci is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 67 tokens to every session and 2,487 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
ci-cd-pipeline-builder
Tier: POWERFUL Category: Engineering Domain: DevOps / Automation.
memstack-deployment-ci-cd-pipeline
Use this skill when the user says 'CI/CD', 'GitHub Actions', 'pipeline', 'continuous integration', 'continuous deployment', 'ci-cd-pipeline', 'automate deploys', or needs to set up automated build, test, and deployment pipelines. Do NOT use for one-time manual deployments.
bitbucket-workflow
Bitbucket best practices for pull requests, Pipelines CI/CD, Jira integration, and Atlassian ecosystem workflows.
devops-cloud
DevOps, cloud infrastructure, and platform engineering. Use when working with AWS, GCP, Azure, Kubernetes, Terraform, CI/CD pipelines, or infrastructure as code.
ci-pipeline
Push current branch and return the pipeline tracking URL (GitLab or GitHub Actions).
relay-recon
Map the full CI/CD pipeline — triggers, build, test, deploy flow — with risk assessment. Use when asked "how does this deploy", "map the pipeline", or "understand CI/CD".