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-hardengit 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-harden)<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-harden"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-harden.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.1 | $0.00056 | $0.01489 |
| Opus 5 | $0.00028 | $0.00745 |
| Sonnet 5 | $0.00011 | $0.00298 |
| Haiku 4.5 | $0.00006 | $0.00149 |
Grade A, and why
ccc-harden 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 6d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-harden — Production Hardening Audit
Audit a site across 11 hardening pillars to confirm it's safe to ship. Read-only by default. Apply safe auto-fixes with --fix.
What it checks
| Pillar | What it verifies |
|---|---|
| 1. Vercel | Project link, env vars, deploy headers, deploy protection, domain |
| 2. GitHub Linkage | Remote URL, branch tracking, .gitignore coverage, working tree clean |
| 3. GitHub Org | Branch protection on main, Dependabot enabled, secret scanning, CODEOWNERS |
| 4. Sentry | SDK installed, DSN set, source maps uploading, alert rules, sample rate |
| 5. PostHog | SDK installed, env vars set, autocapture config, event whitelist |
| 6. Plausible | Script present, site ID, goals, funnels, recent traffic |
| 7. Clarity | Script presence, project ID |
| 8. Google | GA4, Search Console verified, sitemap submitted, Tag Manager |
| 9. Stripe | Keys present, webhook configured, test/live separation |
| 10. Secrets & PII | gitleaks scan, CSP/HSTS/X-Frame headers, .env audit, log scrubbing |
| 11. Cloudflare | DNS health, TLS/SSL, bot management, caching, HTTP/3, WAF |
When to use
✅ Use when:
- Pre-launch checklist for a new site
- Before a security review or compliance audit
- Periodic monthly/quarterly health check
- After a major refactor that touched config files
- When you suspect a leaked secret
🚫 Don't use when:
- Project is pre-MVP / local-only (overkill)
- Quick fix that doesn't touch infra/config (use
$ccc-doctorinstead)
Trigger flow
When the user invokes $ccc-harden:
-
Read
.harden.jsonat project root. If missing, runbash ~/.claude/skills/harden-site/lib/tier.shto auto-classify (production/staging/parked/personal) and generate it. -
Ask the user via AskUserQuestion which mode:
- Audit only (read-only, default — recommended)
- Apply auto-fixes (writes to vercel.json, .gitignore, etc.)
- Single pillar (pick from list of 11)
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.
- 6d ago First seen · 128 lines · 56 tokens per session scan A 5139f7244569
ccc-harden is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 1,489 once invoked, about $0.0003 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
multi-plan-handoff
Auto-detect plan files in conversation context and pass them to multi: execute subagents by reference, not by paraphrase.
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.…
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…
debt-ops-init
Write or refresh a "Tech debt operations" section in the project's AGENTS.md so the team shares one source of truth for debt-ops disciplines. Run ONLY when the user explicitly asks to set up, install, or initialize debt-ops disciplines — never auto-invoke. Idempotent; only the managed section changes, other sections…
debt-ops-metrics
Print a debt-ops health summary from the metrics log, covering registration rate, feedback action rate, ADR creation, and AI-authored share. Use when the user asks for "debt-ops metrics", "debt health", "registry stats", or a tech-debt health summary. Read-only, never writes the log.