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.
npx agentmods add commands/brennercruvinel/ccplugins/fix-todosgit 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/fix-todos)<a href="https://agentmods.dev/commands/brennercruvinel/ccplugins/fix-todos"><img src="https://agentmods.dev/badge/commands/brennercruvinel/ccplugins/fix-todos.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01042 |
| Opus 5 | $0.00000 | $0.00521 |
| Sonnet 5 | $0.00000 | $0.00208 |
| Haiku 4.5 | $0.00000 | $0.00104 |
Grade A, and why
fix-todos 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 5d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix TODOs
I'll systematically find and resolve TODO comments in your codebase with intelligent understanding and continuity across sessions.
Arguments: $ARGUMENTS - files, directories, or specific TODO patterns to fix
Session Intelligence
I'll maintain TODO resolution progress across sessions:
Session Files (in current project directory):
fix-todos/plan.md- All TODOs found and resolution statusfix-todos/state.json- Current progress and decisions
IMPORTANT: Session files are stored in a fix-todos folder in your current project directory
Auto-Detection:
- If session exists: Resume from last TODO
- If no session: Scan and create new plan
- Commands:
resume,status,new
Phase 1: Discovery & Analysis
MANDATORY FIRST STEPS:
- Check if
fix-todosdirectory exists in current working directory - If directory exists, check for session files:
- Look for
fix-todos/state.json - Look for
fix-todos/plan.md - If found, resume from existing session
- Look for
- If no directory or session exists:
- Scan entire codebase for TODOs
- Create categorized plan
- Initialize progress tracking
- Show TODO summary before starting
I'll find and categorize all TODOs:
TODO Detection:
- TODO, FIXME, HACK, XXX markers
- Different priority levels
- Context and complexity assessment
- Related code understanding
Smart Categorization:
- Quick fixes: Simple validations, null checks
- Features: Missing functionality
- Refactoring: Code improvements
- Security: Safety and validation needs
- Performance: Optimization opportunities
Phase 2: Resolution Planning
Based on analysis, I'll create a resolution plan:
Priority Order:
- Security-critical TODOs
- Bug-related TODOs
- Simple improvements
- Feature additions
- Performance optimizations
I'll write this plan to fix-todos/plan.md with:
- Each TODO location and content
- Proposed resolution approach
- Risk assessment
- Implementation order
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.
- 5d ago First seen · 172 lines · 0 tokens per session scan A 2e6d128461c5
fix-todos 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 1,042 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
parallel
You are executing the /hydra:parallel command. Start multiple agents simultaneously in different worktrees.
project
Command "project" from Marcel-Bich/marcel-bich-claude-marketplace, covering credo project target, with an argument (set the pin) and without an argument (show the current target).
status
You are executing the /hydra:status command. Show detailed status of one or all worktrees.
project-estimate
Generate detailed project cost estimates with line items, labor, materials, contingency, and summary breakdowns.
change-order
Draft change order documentation with scope changes, cost impacts, schedule adjustments, and approval routing.
progress-report
Create weekly or monthly progress reports with milestone tracking, budget status, and risk assessments.