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-deploy-checknpx 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.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.00048 | $0.01095 |
| Opus 5 | $0.00024 | $0.00548 |
| Sonnet 5 | $0.00010 | $0.00219 |
| Haiku 4.5 | $0.00005 | $0.00110 |
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 4d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-deploy-check — Pre-deploy readiness gate
Placeholders like ~~CI/CD and ~~monitoring refer to connected tools. See CONNECTORS.md.
Run a pre-deployment readiness check before shipping. Quick Mode runs the essential checklist in under 60 seconds. Power Mode performs a full assessment with rollback plan.
Quick Mode (default)
Run this checklist automatically — no questions needed:
[ ] Tests pass → npm test / vitest / pytest (auto-detect)
[ ] Build is clean → npm run build / tsc --noEmit
[ ] No console.log → grep -r "console\.log" src/ --include="*.ts"
[ ] No hardcoded secrets → scan for API keys, tokens, passwords in diff
[ ] No TODO/FIXME in → grep -r "TODO\|FIXME" src/ (warn, don't block)
changed files
[ ] package.json lock → check for lockfile changes that don't match package.json
[ ] Migrations are safe → check for destructive SQL (DROP, DELETE without WHERE)
Report each check as PASS / WARN / FAIL.
Verdict:
- All PASS → GO — ship it
- Any WARN → CAUTION — review warnings before shipping
- Any FAIL → NO-GO — fix before deploying
Power Mode
Activate by passing --power or detailed or production.
Full deploy readiness assessment:
Pre-Deploy Checks
- All Quick Mode checks (above)
- Diff size — flag if >500 lines changed (increased risk)
- New dependencies — security scan via
npm auditorpip audit - Environment variable diff — any new required env vars documented?
- Feature flags — is the change gated appropriately?
- Database migration — reversible? tested on staging?
Rollback Plan (auto-generated)
## Rollback Plan
- **How to roll back:** `git revert <sha>` + redeploy OR feature flag off
- **Data concerns:** [Are there DB migrations that are hard to reverse?]
- **Estimated rollback time:** [X minutes]
- **Owner on call:** [Who to page if this goes wrong]
Risk Assessment
| Dimension | Risk | Notes |
|---|---|---|
| Scope of change | Low/Med/High | Lines changed, files touched |
| Data mutations | Low/Med/High | Schema changes, data migrations |
| External dependencies | Low/Med/High | New 3rd-party calls |
| Traffic impact | Low/Med/High | Hot paths, rate limits |
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.
- 4d 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 today), licensed MIT. It adds 48 tokens to every session and 1,095 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
claude-code-session-broker
Use when running Arcgentic V2 in Claude Code and fixed Planner, Developer, and Auditor role sessions must be coordinated through a broker.
verify-gates
Runs the mechanical quality gates that the arcgentic state machine requires for state transitions. Invoked indirectly by transition.sh OR directly by orchestrator agent before declaring a state transition. Use when about to call transition.sh OR when manually verifying that a round artifact meets the gate criteria.…
agency-roster
Use when a round references agency-agents catalogs, role-family routing, multi-agent identity prompts, or English/Chinese specialist role catalogs.
cross-session-handoff
Read, write, snapshot, and lock .arcgentic/state.yaml across planner, dev, audit, and optional test sessions.
hook-template
Generate hook script from template. Use when adding a new hook, wiring a PreToolUse/PostToolUse/Stop/Notification hook, or scaffolding hook config for settings.json.
check-environment
Verify Claude, Codex, and Grok availability plus Director guidance, relay, agents, and skills. Audit optional hooks only when selected. Use after installation or when a native surface misbehaves.