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-securitygit 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-security)<a href="https://agentmods.dev/skills/kevinzai/commander/ccc-security"><img src="https://agentmods.dev/badge/skills/kevinzai/commander/ccc-security.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.00036 | $0.01004 |
| Opus 5 | $0.00018 | $0.00502 |
| Sonnet 5 | $0.00007 | $0.00201 |
| Haiku 4.5 | $0.00004 | $0.00100 |
Grade A, and why
ccc-security 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
$ccc-security — Security domain hub
Load ONE skill. Get the entire application security domain. 8 skills in one.
Integration note: This skill invokes Claude Code's built-in /security-review command as the entry point, then routes to specialist sub-skills for deeper analysis. It does not reimplement the security review — it extends it.
Sub-Skills
| # | Skill | Focus |
|---|---|---|
| 1 | security-audit | Comprehensive security audit — SAST, DAST, manual review |
| 2 | prompt-injection-defense | Defend AI-powered apps against prompt injection attacks |
| 3 | dependency-audit | Audit npm/pip/cargo dependencies for known vulnerabilities |
| 4 | secrets-scanner | Scan codebase for hardcoded secrets, API keys, tokens |
| 5 | owasp-top-10 | Check application against OWASP Top 10 vulnerabilities |
| 6 | codeql-integration | Set up CodeQL for automated security analysis in CI |
| 7 | variant-analysis | Find variants of known vulnerabilities across codebase |
| 8 | incident-response | Security incident response playbook and remediation |
No expressed intent? Present the top 3 sub-skills + "More…" as an AskUserQuestion picker (≤4 options).
Routing Matrix
| Your Intent | Route To |
|---|---|
| "Security audit" / "Review for vulnerabilities" | /security-review → security-audit + owasp-top-10 |
| "Prompt injection" / "AI app security" | prompt-injection-defense |
| "Vulnerable dependencies" / "npm audit" | dependency-audit |
| "Hardcoded secrets" / "API key scan" | secrets-scanner |
| "OWASP" / "Top 10 check" | owasp-top-10 |
| "CodeQL" / "Automated security CI" | codeql-integration |
| "Find all variants of this bug" | variant-analysis |
| "Security incident" / "We were breached" | incident-response |
Protocol
- Always start with
/security-reviewbuilt-in — it provides the initial scan surface - Route to specialist skills for deeper analysis per domain
secrets-scanneranddependency-auditon every new projectowasp-top-10before every production releaseincident-responsefor active security events — stop all other work first
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 · 91 lines · 36 tokens per session scan A 36b9619f451b
ccc-security is a skill published in the GitHub repository KevinZai/commander (6 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 1,004 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-09-03.
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-add
Register a deferred decision in the tech-debt registry. Trigger by judgment, not a marker scan, whenever a future reader would ask "why this way?": an unmade decision, stub, loosened type, bypassed check, swallowed error, a default picked "for now", or a TODO/FIXME/HACK/XXX marker. Trigger immediately whenever you…