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 agentmods add commands/brennercruvinel/ccplugins/implementgit clone --depth 1 https://github.com/brennercruvinel/CCPluginsWhat 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 | $0.00000 | $0.02000 |
| Opus 5 | $0.00000 | $0.01000 |
| Sonnet 5 | $0.00000 | $0.00400 |
| Haiku 4.5 | $0.00000 | $0.00200 |
Grade A, and why
implement 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 2d 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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Smart Implementation Engine
I'll intelligently implement features from any source - adapting them perfectly to your project's architecture while maintaining your code patterns and standards.
Arguments: $ARGUMENTS - URLs, paths, or descriptions of what to implement
Session Intelligence
I'll check for existing implementation sessions to continue seamlessly:
Session Files (in current project directory):
implement/plan.md- Current implementation plan and progressimplement/state.json- Session state and checkpoints
IMPORTANT: Session files are stored in a implement folder in your current project root, NOT in home directory or parent folders. If a session exists, I'll resume from the exact checkpoint. Otherwise, I'll create a new implementation plan and track progress throughout.
Phase 1: Initial Setup & Analysis
MANDATORY FIRST STEPS:
- Check if
implementdirectory exists in current working directory - If directory exists, check for session files:
- Look for
implement/state.json - Look for
implement/plan.md - If found, resume from existing session
- Look for
- If no directory or session exists:
- Create
implement/plan.md - Initialize
implement/state.json
- Create
- Complete full analysis BEFORE any implementation
Critical: Use implement folder in current directory. Do NOT use $HOME/implement or any parent directory paths
I'll examine what you've provided and your project structure:
Source Detection:
- Web URLs (GitHub, GitLab, CodePen, JSFiddle, documentation sites)
- Local paths (files, folders, existing code)
- Implementation plans (.md files with checklists)
- Feature descriptions for research
Project Understanding:
- Architecture patterns using Glob and Read
- Existing dependencies and their versions
- Code conventions and established patterns
- Testing approach and quality standards
Phase 2: Strategic Planning
Based on my analysis, I'll create an implementation plan:
Plan Creation:
- Map source features to your architecture
- Identify dependency compatibility
- Design integration approach
- Break work into testable chunks
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.
- 2d ago First seen · 303 lines · 0 tokens per session scan A c45b5f49a2bc
implement is a command published in the GitHub repository brennercruvinel/CCPlugins (2,780 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,000 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
README
Git workflow and quality assurance commands for the claude-skills repository.
convert-to-todowrite-tasklist-prompt
Purpose: Transform verbose, context-heavy slash commands into efficient TodoWrite tasklist-based methods with parallel subagent execution for 60-70% speed improvements.
security-audit
Perform a comprehensive security audit of the codebase to identify potential vulnerabilities, insecure patterns, and security best practice violations.
save
Save a key-value memory entry to persistent storage.
medical-necessity
Generate medical necessity letters citing chiropractic clinical guidelines for insurance authorization and appeals.
rfi-response
Compose professional RFI responses with technical clarifications, drawing references, and resolution documentation.