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/cleanprojectgit 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.00525 |
| Opus 5 | $0.00000 | $0.00262 |
| Sonnet 5 | $0.00000 | $0.00105 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
cleanproject 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clean Project
I'll help clean up development artifacts while preserving your working code.
Strategic Thinking Process
-
Artifact Identification
- What patterns indicate temporary/debug files?
- Which files might look temporary but are actually important?
- Are there project-specific conventions for temp files?
- What about generated files that should be kept?
-
Safety Analysis
- Which deletions are definitely safe?
- Which require more careful inspection?
- Are there active processes using these files?
- Could removing these break the development environment?
-
Common Pitfalls
- .env files might look like artifacts but contain config
- .cache directories might be needed for performance
- Some .tmp files might be active session data
- Debug logs might contain important error information
-
Cleanup Strategy
- Start with obvious artifacts (*.log, *.tmp, *~)
- Check file age - older files are usually safer to remove
- Verify with git status what's tracked vs untracked
- Group similar files for batch decision making
Based on this analysis, I'll create a git checkpoint for safety:
git add -A
git commit -m "Pre-cleanup checkpoint" || echo "No changes to commit"
Important: I will NEVER:
- Add "Co-authored-by" or any Claude signatures
- Include "Generated with Claude Code" or similar messages
- Modify git config or user credentials
- Add any AI/assistant attribution to the commit
- Use emojis in commits, PRs, or git-related content
I'll identify cleanup targets using native tools:
- Glob tool to find temporary and debug files
- Grep tool to detect debug statements in code
- Read tool to verify file contents before removal
Critical directories are automatically protected:
- .claude directory (commands and configurations)
- .git directory (version control)
- node_modules, vendor (dependency directories)
- Essential configuration files
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 · 71 lines · 0 tokens per session scan A dfc0088f557f
cleanproject 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 525 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.