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/doccker/cc-use-exp/cc-core-defensivenpx skills add doccker/cc-use-exp --skill cc-core-defensivegit clone --depth 1 https://github.com/doccker/cc-use-expWrote 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/doccker/cc-use-exp/cc-core-defensive)<a href="https://agentmods.dev/skills/doccker/cc-use-exp/cc-core-defensive"><img src="https://agentmods.dev/badge/skills/doccker/cc-use-exp/cc-core-defensive.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.00064 | $0.00376 |
| Opus 5 | $0.00032 | $0.00188 |
| Sonnet 5 | $0.00013 | $0.00075 |
| Haiku 4.5 | $0.00006 | $0.00038 |
Grade A, and why
cc-core-defensive 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
4 files 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.
- 6d ago First seen · 40 lines · 64 tokens per session scan A 42d0ae45cc2e
cc-core-defensive is a skill published in the GitHub repository doccker/cc-use-exp (1,039 stars, last pushed 10d ago), with no licence file. It adds 64 tokens to every session and 376 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-30.
Other skills, from other repositories
antigravity-cli
Delegate heavy, multi-step, or specialized tasks to Google's Antigravity CLI agents. Use when a task would benefit from: (1) deep multi-file codebase analysis across many files, (2) web research with Google Search grounding, (3) image generation or visual assets, (4) a second AI perspective for code review or…
conductor-new-track
Plans a new track (feature or bug fix), generates spec/plan documents, and updates the registry.
mantis-plan
Formulates a targeted defensive security reviewing plan based on the active threat model and historical learnings. Use when starting a security review campaign to map the codebase boundaries and generate a roadmap (workspace/plan.json). Don't use for executing code reviews, writing test scripts, or patching code.
mantis-report
Generates a human-readable security review packet compiled from confirmed findings and exploit chains. Use at the end of a review cycle to produce stakeholder-facing documentation. Don't use for auditing code or verifying patches directly.
mantis-dedupe
Consolidates raw security findings to eliminate redundant reports. Use when raw findings have been generated by the researcher and need consolidation before review. Don't use for initial code auditing or patch generation.
mantis-history
Analyzes the repository's version control system (VCS) history to extract past vulnerabilities, security fixes, and vulnerability patterns. Use as an initial pre-processing step to build a historical vulnerabilities database (workspace/historicallearnings.jsonl) that informs subsequent stages about past issues and…