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-deploy-checkgit 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-deploy-check)<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-deploy-check"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-deploy-check/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-deploy-check"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-deploy-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00074 | $0.02192 |
| Opus 5.5 | $0.00030 | $0.00877 |
| Sonnet 5.5 | $0.00015 | $0.00438 |
| Haiku 4.5 | $0.00007 | $0.00219 |
Grade A, and why
ccc-deploy-check 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 8d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-deploy-check — Pre-deploy readiness gate
CC Commander · $ccc-deploy-check · a GO, CAUTION or NO-GO verdict before anything goes live
Placeholders like ~~CI/CD and ~~monitoring refer to connected tools, which are opt-in and absent by default. See CONNECTORS.md.
When to use / when not to
- Use before any deploy. Quick mode runs by default; power mode adds risk assessment and a rollback plan.
- This skill only reads. To deploy, use
$ccc-deploy; for the full ship menu (pre-flight matrix, release tagging), use$ccc-ship. - In Codex, ask the picker as a plain-text question; run the power-mode verifier with
codex execin a fresh session, read-only.
What happens
1. Resolve the base and changed files
BASE_REF=$(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null || echo main)
BASE=$(git merge-base HEAD "$BASE_REF")
git diff --name-only --diff-filter=ACM "$BASE"...HEAD
git diff --shortstat "$BASE"...HEAD
If there is no remote or no diff, check the working tree against HEAD instead and say so.
2. Quick mode (default)
Run every check, no questions. Report each as PASS, WARN or FAIL.
| Check | Command | Result |
|---|---|---|
| Tests pass | npm test · npx vitest run · pytest (auto-detect from package.json scripts, pyproject.toml, pytest.ini) |
non-zero exit → FAIL |
| Build is clean | npm run build if the script exists, else npx tsc --noEmit with a tsconfig.json |
non-zero exit → FAIL |
| No console.log | grep -rn "console\.log" src/ --include="*.ts" --include="*.tsx" --include="*.js" limited to changed files |
hits → WARN |
| No hardcoded secrets | the secret scan below, on changed files | any hit → FAIL |
| No TODO/FIXME in changed files | grep -n "TODO|FIXME" on changed files |
hits → WARN, never blocks |
| Lockfile consistent | package.json and its lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock) changed together |
one without the other → WARN |
| Migrations are safe | the migration grep below, on changed *.sql and migration files |
DROP/TRUNCATE, or DELETE without WHERE → FAIL |
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.
- 8d ago Changed · +48 lines · +26 tokens per session f0d7e10acb56
- 1mo ago First seen · 119 lines · 48 tokens per session scan A e2046d28a91b
ccc-deploy-check is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed yesterday), licensed MIT. It adds 74 tokens to every session and 2,192 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
uninstall
Remove Multi startup files while preserving provider credentials.
login
Start the official Cursor SDK login flow.
skill-dev
Use this skill when creating or refining Claude Code skill definitions. Skills are model-invoked capabilities that Claude activates autonomously based on context. Helps design focused skills with discovery-optimized descriptions, proper directory structures, and supporting resources. Automatically invoked when user…
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.…
coordinator
Runs the research-team plugin's multi-agent research pipeline end-to-end from the main thread: decomposes a topic into 2-5 subtopics, spawns parallel research-team:research-specialist subagents for each, verifies their output on disk, then spawns a research-team:research-report-writer subagent to synthesize the final…
mcp-tool-dev
Create MCP tools — individual tool functions exposed via Model Context Protocol. Use this skill whenever users mention MCP tools, tool handlers, tool functions, tool definitions, or want to add capabilities to an MCP server. Also use when the conversation involves designing tool schemas, writing tool descriptions, or…