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-importsgit 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-imports)<a href="https://agentmods.dev/commands/brennercruvinel/ccplugins/fix-imports"><img src="https://agentmods.dev/badge/commands/brennercruvinel/ccplugins/fix-imports.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.00955 |
| Opus 5 | $0.00000 | $0.00477 |
| Sonnet 5 | $0.00000 | $0.00191 |
| Haiku 4.5 | $0.00000 | $0.00096 |
Grade A, and why
fix-imports 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix Broken Imports
I'll systematically fix import statements broken by file moves or renames, with full continuity across sessions.
Arguments: $ARGUMENTS - specific paths or import patterns to fix
Session Intelligence
I'll maintain import fixing progress:
Session Files (in current project directory):
fix-imports/plan.md- All broken imports and fixesfix-imports/state.json- Resolution progress
IMPORTANT: Session files are stored in a fix-imports folder in your current project root
Auto-Detection:
- If session exists: Resume from last import
- If no session: Scan for broken imports
- Commands:
resume,status,new
Phase 1: Import Analysis
MANDATORY FIRST STEPS:
- Check if
fix-importsdirectory exists in current working directory - If directory exists, check for session files:
- Look for
fix-imports/state.json - Look for
fix-imports/plan.md - If found, resume from existing session
- Look for
- If no directory or session exists:
- Scan for all broken imports
- Create fix plan
- Initialize progress tracking
- Show import issues summary
Note: Always look for session files in the current project's fix-imports/ folder, not ../../../fix-imports/
I'll detect broken imports:
Import Patterns:
- File not found errors
- Module resolution failures
- Moved or renamed files
- Deleted dependencies
- Circular references
Smart Detection:
- Language-agnostic scanning
- Path alias understanding
- Barrel export recognition
- External vs internal imports
Phase 2: Resolution Planning
Based on analysis, I'll create resolution plan:
Resolution Strategy:
- Exact filename matches
- Similar name suggestions
- Export symbol search
- Path recalculation
- Import removal if needed
I'll write this plan to fix-imports/plan.md with:
- Each broken import location
- Possible resolutions
- Confidence level
- Fix approach
Phase 3: Intelligent Fixing
I'll fix imports matching your patterns:
Resolution Patterns:
- Update relative paths correctly
- Maintain path alias usage
- Preserve import grouping
- Follow sorting conventions
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 · 168 lines · 0 tokens per session scan A a4c625b354b8
fix-imports 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 955 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).
watch
You are executing the /hydra:watch command. Live monitoring of all background agents with real-time status updates.
save
Save a key-value memory entry to persistent storage.