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/talayash/agentrium/refactor-cleanergit clone --depth 1 https://github.com/talayash/agentriumWhat 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.00615 |
| Opus 5 | $0.00026 | $0.00308 |
| Sonnet 5 | $0.00010 | $0.00123 |
| Haiku 4.5 | $0.00005 | $0.00061 |
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 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.
This is a copy
91% identical to refactor-cleaner — 6 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 — 86 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.
- 2d ago First seen · 86 lines · 51 tokens per session scan A 30ed8fae5a0b
refactor-cleaner is an agent published in the GitHub repository talayash/agentrium (39 stars, last pushed 2d ago), licensed MIT. It adds 51 tokens to every session and 615 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to refactor-cleaner, differing in 6 lines, and is treated as a copy.
Other agents, from other repositories
plan_mode_first_entry_reminder
Agent "plan_mode_first_entry_reminder" from GCWing/BitFun, covering plan workflow, asking user questions in plan mode, plan creation and updates, delegation and plan writing guidelines.
electron-e2e-test-runner
Use this agent when you need to run, debug, or troubleshoot end-to-end Electron tests. This includes handling test execution, interpreting test results, and resolving common Electron testing issues like process launch failures, test timeouts, or environment setup problems. Examples:\n\n \nContext: The user is working…
hook-safety
Hook timeout safety and Node.js ESM conventions reviewer. Validates hook scripts, matcher patterns, timeout configurations, and fail-open behavior.
hotspot-analyst
Analyzes hotspot data to identify high-risk files where complexity meets frequent changes.
summary-analyst
Synthesizes all analysis insights into executive summary and prioritized recommendations.
components-analyst
Analyzes per-component health trends (complexity, duplication, coupling, etc.).