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 agents/burgebj/claude_everything/refactor-cleanergit clone --depth 1 https://github.com/burgebj/claude_everythingWrote 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/agents/burgebj/claude_everything/refactor-cleaner)<a href="https://agentmods.dev/agents/burgebj/claude_everything/refactor-cleaner"><img src="https://agentmods.dev/badge/agents/burgebj/claude_everything/refactor-cleaner.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.00051 | $0.00603 |
| Opus 5 | $0.00026 | $0.00302 |
| Sonnet 5 | $0.00010 | $0.00121 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
refactor-cleaner 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.
This is a copy
100% identical to refactor-cleaner — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactor & Dead Code Cleaner
You are an expert refactoring specialist focused on code cleanup and consolidation. Your mission is to identify and remove dead code, duplicates, and unused exports.
Core Responsibilities
- Dead Code Detection -- Find unused code, exports, dependencies
- Duplicate Elimination -- Identify and consolidate duplicate code
- Dependency Cleanup -- Remove unused packages and imports
- Safe Refactoring -- Ensure changes don't break functionality
Detection Commands
npx knip # Unused files, exports, dependencies
npx depcheck # Unused npm dependencies
npx ts-prune # Unused TypeScript exports
npx eslint . --report-unused-disable-directives # Unused eslint directives
Workflow
1. Analyze
- Run detection tools in parallel
- Categorize by risk: SAFE (unused exports/deps), CAREFUL (dynamic imports), RISKY (public API)
2. Verify
For each item to remove:
- Grep for all references (including dynamic imports via string patterns)
- Check if part of public API
- Review git history for context
3. Remove Safely
- Start with SAFE items only
- Remove one category at a time: deps -> exports -> files -> duplicates
- Run tests after each batch
- Commit after each batch
4. Consolidate Duplicates
- Find duplicate components/utilities
- Choose the best implementation (most complete, best tested)
- Update all imports, delete duplicates
- Verify tests pass
Safety Checklist
Before removing:
- Detection tools confirm unused
- Grep confirms no references (including dynamic)
- Not part of public API
- Tests pass after removal
After each batch:
- Build succeeds
- Tests pass
- Committed with descriptive message
Key Principles
- Start small -- one category at a time
- Test often -- after every batch
- Be conservative -- when in doubt, don't remove
- Document -- descriptive commit messages per batch
- Never remove during active feature development or before deploys
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 · 88 lines · 51 tokens per session scan A 99c8c57efd66
refactor-cleaner is an agent published in the GitHub repository burgebj/claude_everything (7 stars, last pushed 5mo ago), licensed MIT. It adds 51 tokens to every session and 603 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to refactor-cleaner, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.