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
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/brennercruvinel/CCPluginsnpx agentmods add commands/brennercruvinel/ccplugins/refactorWrote 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/refactor)<a href="https://agentmods.dev/commands/brennercruvinel/ccplugins/refactor"><img src="https://agentmods.dev/badge/commands/brennercruvinel/ccplugins/refactor/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/refactor"><img src="https://agentmods.dev/badge/commands/brennercruvinel/ccplugins/refactor.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.02563 |
| Opus 5.5 | $0.00000 | $0.01025 |
| Sonnet 5.5 | $0.00000 | $0.00513 |
| Haiku 4.5 | $0.00000 | $0.00256 |
Grade A, and why
refactor 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 — 378 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intelligent Refactoring Engine
I'll help you restructure your code systematically - preserving functionality while improving structure, readability, and maintainability.
Arguments: $ARGUMENTS - files, directories, or refactoring scope
KEY FEATURE: Built-in validation and refinement after EVERY change ensures nothing breaks and no code is left behind. The AI will automatically fix its own mistakes during the refactoring process.
SESSION FILES LOCATION: Always use refactor/ folder in current directory
Session Intelligence
I'll maintain refactoring continuity across sessions:
Session Files (in current project):
refactor/plan.md- Refactoring plan with progress trackingrefactor/state.json- Current state and completed actions
IMPORTANT: The refactor folder is created in your CURRENT PROJECT directory. Use refactor/ to access it.
Auto-Detection:
- If session exists: Resume from last checkpoint
- If no session: Create new refactoring plan
- Commands:
resume,continue,status,new
EXAMPLE OF CORRECT PATH USAGE:
# CORRECT - looks in current project:
Read refactor/state.json
LS refactor
# WRONG - these will fail:
Read ../../../refactor/state.json
Read $HOME/.claude/refactor/state.json
Phase 1: Initial Setup & Analysis
Extended Thinking for Complex Refactoring
For complex refactoring scenarios, I'll use extended thinking to develop comprehensive strategies:
Triggers for Extended Analysis:
- Large-scale architectural changes
- Complex dependency untangling
- Performance-critical refactoring
- Legacy system modernization
MANDATORY FIRST STEPS FOR SESSION CHECK:
Step 1: Check for refactor directory in CURRENT directory
Command: LS refactor
Step 2: If refactor exists, read session files:
Command: Read refactor/state.json
Command: Read refactor/plan.md
DO NOT USE THESE WRONG PATHS:
- ../../../refactor/ (WRONG - goes up directories)
- $HOME/refactor/ (WRONG - home directory)
- ~/refactor/ (WRONG - home directory)
ONLY USE: refactor/ (current directory)
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 · 378 lines · 0 tokens per session scan A 25a89083392d
refactor 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 2,563 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
security-audit
Perform a comprehensive security audit of the codebase to identify potential vulnerabilities, insecure patterns, and security best practice violations.
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.
anchors
List what each requirement tag anchors to (read-only).
advanced-code-review-context
Advanced Code Review Phase 2: Context Analysis - load previous reviews, PR history, declined items.
code-review-give
Give mode for code-review: Review someone else's code with multi-pass analysis and structured recommendations.
mach12:issue-review
Read a GitHub issue and all comments, review the implementation plan, and present findings.