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/find-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/find-todos)<a href="https://agentmods.dev/commands/brennercruvinel/ccplugins/find-todos"><img src="https://agentmods.dev/badge/commands/brennercruvinel/ccplugins/find-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.1 | $0.00000 | $0.00319 |
| Opus 5 | $0.00000 | $0.00160 |
| Sonnet 5 | $0.00000 | $0.00064 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
find-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 6d 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.
What it actually says
Find Development Tasks
I'll locate all TODO comments and unfinished work markers in your codebase.
I'll use the Grep tool to efficiently search for task markers with context:
- Pattern: "TODO|FIXME|HACK|XXX|NOTE"
- Case insensitive search across all source files
- Show surrounding lines for better understanding
For each marker found, I'll show:
- File location with line number
- The full comment with context
- Surrounding code to understand what needs to be done
- Priority assessment based on the marker type
When I find multiple items, I'll create a todo list to organize them by priority:
- Critical (FIXME, HACK, XXX): Issues that could cause problems
- Important (TODO): Features or improvements needed
- Informational (NOTE): Context that might need attention
I'll also identify:
- TODOs that reference missing implementations
- Placeholder code that needs replacement
- Incomplete error handling
- Stubbed functions awaiting implementation
After scanning, I'll ask: "Convert these to GitHub issues?"
- Yes: I'll create properly categorized issues
- Todos only: I'll maintain the local todo list
- Summary: I'll provide organized report
Important: I will NEVER:
- Add "Created by Claude" or any AI attribution to issues
- Include "Generated with Claude Code" in descriptions
- Modify repository settings or permissions
- Add any AI/assistant signatures or watermarks
This helps track and prioritize unfinished work systematically.
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.
- 6d ago First seen · 38 lines · 0 tokens per session scan A 0bb245adfa31
find-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 319 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.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
update-counts
Update all hardcoded counts (skills, agents, marketplace repos/skills) across documentation from filesystem.
save
Save a key-value memory entry to persistent storage.