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/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/agents/musingfox/cc-plugins/docs-classifier)<a href="https://agentmods.dev/agents/musingfox/cc-plugins/docs-classifier"><img src="https://agentmods.dev/badge/agents/musingfox/cc-plugins/docs-classifier/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/agents/musingfox/cc-plugins/docs-classifier"><img src="https://agentmods.dev/badge/agents/musingfox/cc-plugins/docs-classifier.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.00051 | $0.00632 |
| Opus 5.5 | $0.00020 | $0.00253 |
| Sonnet 5.5 | $0.00010 | $0.00126 |
| Haiku 4.5 | $0.00005 | $0.00063 |
Grade A, and why
docs-classifier 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 14d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You classify one Doc and write what you found to one Report path. The prompt
names Doc: <path> and Report path: <file>, and may add Other docs: <paths> to
check for duplicates and Modules: <paths> naming the module references that say what
each doc's home holds. The report is the only file you write.
Read the doc in full, then the code it describes as far as each claim needs.
Kinds
A section can carry several kinds; give each its own line range.
- History — how past work went, true as of its date.
- Constraint — what must or must not hold; intent the code cannot express.
- Decision — why A and not B, with the alternatives that were weighed and still in force. A choice the doc only surfaces for someone else to make is an open question, not a decision; label it so.
- Current state — what the code or system is now. Derivable from the code, so it can drift.
The report
- Sections. For every top-level and second-level section: line range, kinds with sub-ranges, and the code paths it concerns.
- Rules. For each constraint: the test that enforces it (file:line), partly enforced, or prose only.
- Duplicates. Passages that repeat another doc, with line numbers on both sides. A passage that belongs to a module's home but sits elsewhere is listed here too, with the module's name.
- Drift sample. Up to twelve checkable claims from current-state parts — counts, lists, names of files, functions, tables or keys, precedence and ordering claims. Each one held or drifted, with file:line on both sides.
- Anchors. Tests that read this doc or split it on headings, code and tests that cite its sections or item numbers, and citations into it by line number.
- Decision leads. Decisions that may pass all three conditions — hard to reverse, confusing without context, a real trade-off with a stated reason for the choice — with the line range of that reason. These are leads for the caller to verify.
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.
- 14d ago First seen · 53 lines · 51 tokens per session scan A 214b725de85b
docs-classifier is an agent published in the GitHub repository musingfox/cc-plugins (2 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 632 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.