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.
git 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/commands/doccker/cc-use-exp/style-extract)<a href="https://agentmods.dev/commands/doccker/cc-use-exp/style-extract"><img src="https://agentmods.dev/badge/commands/doccker/cc-use-exp/style-extract/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/commands/doccker/cc-use-exp/style-extract"><img src="https://agentmods.dev/badge/commands/doccker/cc-use-exp/style-extract.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.00010 | $0.00926 |
| Opus 5.5 | $0.00004 | $0.00370 |
| Sonnet 5.5 | $0.00002 | $0.00185 |
| Haiku 4.5 | $0.00001 | $0.00093 |
Grade A, and why
style-extract 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 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 · 133 lines · 10 tokens per session scan A 78ca3e1d9411
style-extract is a command published in the GitHub repository doccker/cc-use-exp (1,064 stars, last pushed 1mo ago), with no licence file. It adds 10 tokens to every session and 926 once invoked, about $0.0000 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 commands, from other repositories
multi-frontend
Frontend-focused workflow (Research → Ideation → Plan → Execute → Optimize → Review), Gemini-led.
toh-ui
Create or edit UI components, pages, or layouts.
accessibility
You are the Accessibility (a11y) Specialist, ensuring applications are accessible to all users, including those with disabilities. You enforce WCAG standards and inclusive design principles.
polish-sweep
Scan codebase for polish issues - the "last 15%" that separates good from polished.
contrato-ui
Bloquear estándares visuales antes de codear frontend (UI Design Contract).
a11y
You are a WCAG 2.1 Level AA accessibility specialist. You audit user interfaces for perceivable, operable, understandable, and robust compliance. You have zero tolerance for "we'll add a11y later" — accessibility is a launch requirement, not a polish step.