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/make-it-prettygit 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.00513 |
| Opus 5 | $0.00000 | $0.00257 |
| Sonnet 5 | $0.00000 | $0.00103 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
make-it-pretty 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 3d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Make It Pretty
I'll improve code readability while preserving exact functionality.
Strategic Thinking Process
-
Code Analysis
- What makes this code "ugly" or hard to read?
- Are there complex nested structures that need simplification?
- Is the naming unclear or inconsistent?
- Are there repeated patterns that could be abstracted?
-
Safety Considerations
- Which changes are purely cosmetic (safe)?
- Which might affect behavior (risky)?
- Are there implicit dependencies on current structure?
- Could renaming break external references?
-
Improvement Strategy
- Priority 1: Clear naming (variables, functions, files)
- Priority 2: Reduce complexity (extract functions, simplify logic)
- Priority 3: Remove redundancy (DRY principle)
- Priority 4: Improve type safety (if applicable)
-
Validation Approach
- How can I ensure functionality remains identical?
- What tests exist to verify behavior?
- Should I add temporary logging to verify flow?
Based on this analysis, I'll proceed safely:
Safety First:
- Create git checkpoint before changes
- Use Write tool to create backups
- Track all modifications systematically
I'll identify files to beautify based on:
- Files you specify, or if none specified, analyze the entire application
- Recently modified code
- Our conversation context
Improvements I'll Make:
- Variable and function names for clarity
- Code organization and structure
- Remove unused code and clutter
- Simplify complex expressions
- Group related functionality
- Fix loose or generic type declarations
- Add missing type annotations where supported
- Make types more specific based on usage
My Approach:
- Analyze current code patterns and type usage
- Apply consistent naming conventions
- Improve type safety where applicable
- Reorganize for better readability
- Remove redundancy without changing logic
Quality Assurance:
- All functionality remains identical
- Tests continue to pass (if available)
- No behavior changes occur
- Clear commit messages for changes
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.
- 3d ago First seen · 75 lines · 0 tokens per session scan A 1a111cfdad3a
make-it-pretty 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 513 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).
hunt
Active vulnerability hunt against a target by invoking tools/hunt.py (which calls vulnscanner.sh against recon/ /). Auto-runs recon first if no recon dir exists. Usage: /hunt target.com.
writing:review
Exhaustive parallel editorial review of written content.