CCPlugins is a collection of commands that extends the Claude Code command-line tool with structured development workflows. Developers use it to automate repetitive coding tasks, and the catalogue entries are its commands and related configuration.
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/brennercruvinel/CCPluginsWrote 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/brennercruvinel/ccplugins/docs)<a href="https://agentmods.dev/commands/brennercruvinel/ccplugins/docs"><img src="https://agentmods.dev/badge/commands/brennercruvinel/ccplugins/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/commands/brennercruvinel/ccplugins/docs"><img src="https://agentmods.dev/badge/commands/brennercruvinel/ccplugins/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.00000 | $0.01627 |
| Opus 5.5 | $0.00000 | $0.00651 |
| Sonnet 5.5 | $0.00000 | $0.00325 |
| Haiku 4.5 | $0.00000 | $0.00163 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Manager
I'll intelligently manage your project documentation by analyzing what actually happened and updating ALL relevant docs accordingly.
My approach:
- Analyze our entire conversation - Understand the full scope of changes
- Read ALL documentation files - README, CHANGELOG, docs/*, guides, everything
- Identify what changed - Features, architecture, bugs, performance, security, etc
- Update EVERYTHING affected - Not just one file, but all relevant documentation
- Maintain consistency - Ensure all docs tell the same story
I won't make assumptions - I'll look at what ACTUALLY changed and update accordingly. If you refactored the entire architecture, I'll update architecture docs, README, migration guides, API docs, and anything else affected.
Mode 1: Documentation Overview (Default)
When you run /docs without context, I'll:
- Glob all markdown files (README, CHANGELOG, docs/*)
- Read each documentation file
- Analyze documentation coverage
- Present organized summary
Output format:
DOCUMENTATION OVERVIEW
├── README.md - [status: current/outdated]
├── CHANGELOG.md - [last updated: date]
├── CONTRIBUTING.md - [completeness: 85%]
├── docs/
│ ├── API.md - [status]
│ └── architecture.md - [status]
└── Total coverage: X%
KEY FINDINGS
- Missing: Setup instructions
- Outdated: API endpoints (3 new ones)
- Incomplete: Testing guide
Mode 2: Smart Update
When you run /docs update or after implementations, I'll:
-
Run
/understandto analyze current codebase -
Compare code reality vs documentation
-
Identify what needs updating:
- New features not documented
- Changed APIs or interfaces
- Removed features still in docs
- New configuration options
- Updated dependencies
-
Update systematically:
- README.md with new features/changes
- CHANGELOG.md with version entries
- API docs with new endpoints
- Configuration docs with new options
- Migration guides if breaking changes
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 · 219 lines · 0 tokens per session scan A 4303f873e000
docs is a command published in the GitHub repository brennercruvinel/CCPlugins (2,775 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,627 tokens. 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
CLAUDE
Last Updated: Mon Oct 27 19:39:26 CST 2025.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
amp-register
Register your agent with an external AMP provider for cross-provider messaging.