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 doccker/cc-use-exp --skill cc-api-proxy-safetygit 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-api-proxy-safety)<a href="https://agentmods.dev/skills/doccker/cc-use-exp/cc-api-proxy-safety"><img src="https://agentmods.dev/badge/skills/doccker/cc-use-exp/cc-api-proxy-safety/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/doccker/cc-use-exp/cc-api-proxy-safety"><img src="https://agentmods.dev/badge/skills/doccker/cc-use-exp/cc-api-proxy-safety.svg" alt="Reviewed on agentmods" width="80" 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.00076 | $0.01223 |
| Opus 5.5 | $0.00030 | $0.00489 |
| Sonnet 5.5 | $0.00015 | $0.00245 |
| Haiku 4.5 | $0.00008 | $0.00122 |
Grade A, and why
cc-api-proxy-safety 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 1mo 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
1 file 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.
- 1mo ago First seen · 129 lines · 76 tokens per session scan A fdbe73d74373
cc-api-proxy-safety is a skill published in the GitHub repository doccker/cc-use-exp (1,064 stars, last pushed 1mo ago), with no licence file. It adds 76 tokens to every session and 1,223 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-30.
Other skills, from other repositories
debugging-expert
Professional Debugging Expert skill. Build performant, secure, and scalable backend logic and RESTful or GraphQL APIs.
profiling-guide
Professional Profiling Guide Expert skill. Build performant, secure, and scalable backend logic and RESTful or GraphQL APIs.
api-integration-architect
Design, implement, debug, and optimize API integrations with expert-level patterns for REST, GraphQL, webhooks, and authentication flows.
agenttrace-session-audit
Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.
api-analyzer
Validates whether an API request is correct based on provided inputs (method, URL, headers, body, auth, query params).
mantis-critic
Assesses the production viability of findings, filtering out debug-only features and assertion traps. Use when findings have been validated and you need to confirm they are triggerable in production release builds (with assertions disabled). Don't use for writing reproduction scripts or patches.