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 musingfox/cc-plugins --skill docsgit clone --depth 1 https://github.com/musingfox/cc-pluginsWrote 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/musingfox/cc-plugins/docs)<a href="https://agentmods.dev/skills/musingfox/cc-plugins/docs"><img src="https://agentmods.dev/badge/skills/musingfox/cc-plugins/docs/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/musingfox/cc-plugins/docs"><img src="https://agentmods.dev/badge/skills/musingfox/cc-plugins/docs.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.00045 | $0.01890 |
| Opus 5.5 | $0.00018 | $0.00756 |
| Sonnet 5.5 | $0.00009 | $0.00378 |
| Haiku 4.5 | $0.00005 | $0.00189 |
Grade A, and why
docs 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 10d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit repository docs
A doc earns its place by carrying what the code cannot say: why a choice was made, what must not change, and lookups too expensive to redo. Everything else the code already says, and a doc restating it is a cache that drifts.
Every section of a doc is one of four kinds. The kind decides who wins when the doc and the code disagree:
| Kind | What it holds | When it disagrees with the code |
|---|---|---|
| History | how past work went, true as of its date | nothing to sync; a new record supersedes it, and a header that claims it is current gets marked historical |
| Constraint | what must or must not hold | the code may be the bug: the human decides before either side changes |
| Decision | why A and not B, still in force | the human decides; a changed decision gets a new record, the old reason stays |
| Current state | what the code or system is now | the code wins, and the doc is fixed in the same change |
Only current state is a cache, and it is where drift lives: counts, lists, maps, precedence claims.
Core and modules
Every repo gets the core. README.md tells a human what the project is and how to
install and use it. The root CLAUDE.md carries the rules and pointers every session
needs, and points at the README instead of restating it. AGENTS.md follows the rules in
references/platform.md.
Everything else is a module. Read a module's reference only when its signal fires, so an audit of a small repo loads the core alone.
| Module | Reference | Signal |
|---|---|---|
| Architecture | architecture.md | an ARCHITECTURE.md; a codemap inside another doc; more than about 10,000 lines of code |
| Contributing | contributing.md | a CONTRIBUTING file in the root, docs/ or .github/; process rules inside CLAUDE.md; hooks the repo itself sets, found with git config --show-origin core.hooksPath and .git/hooks |
| Nested | nested.md | a CLAUDE.md or AGENTS.md below the root; .claude/rules/; workspaces or package manifests below the root; a rule that matters in one directory |
| Invariants, decisions, terms | load /spec:spec, /adr:adr or /spec:glossary before editing an entry |
docs/spec/, docs/decisions/ or docs/adr/, CONTEXT.md; a constraint or decision candidate |
| UI design | design.md | a DESIGN.md; a frontend framework, design tokens or stylesheets |
| Operations | operations.md | IaC or deploy config: terraform, wrangler.*, compose files, k8s manifests |
What ships with it
6 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.
- 10d ago Changed · +3 lines 6de867939f17
- 14d ago First seen · 137 lines · 45 tokens per session scan A 438395fd31d4
docs is a skill published in the GitHub repository musingfox/cc-plugins (2 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 1,890 once invoked, about $0.0002 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-10-02.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…