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.
git clone --depth 1 https://github.com/vibeeval/vibecosystemWrote 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/vibeeval/vibecosystem/refactor-cleaner)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/refactor-cleaner"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/refactor-cleaner/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/agents/vibeeval/vibecosystem/refactor-cleaner"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/refactor-cleaner.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.00051 | $0.01915 |
| Opus 5.5 | $0.00020 | $0.00766 |
| Sonnet 5.5 | $0.00010 | $0.00383 |
| Haiku 4.5 | $0.00005 | $0.00192 |
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 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- refactor-cleaner — 98% identical, 1 lines differ
- refactor-cleaner — 88% identical, 32 lines differ
- refactor-cleaner — 84% identical, 11 lines differ
How it starts
The opening of the file, as written. The whole thing — 308 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 to keep the codebase lean and maintainable.
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
- Documentation - Track all deletions in DELETION_LOG.md
Tools at Your Disposal
Detection Tools
- knip - Find unused files, exports, dependencies, types
- depcheck - Identify unused npm dependencies
- ts-prune - Find unused TypeScript exports
- eslint - Check for unused disable-directives and variables
Analysis Commands
# Run knip for unused exports/files/dependencies
npx knip
# Check unused dependencies
npx depcheck
# Find unused TypeScript exports
npx ts-prune
# Check for unused disable-directives
npx eslint . --report-unused-disable-directives
Refactoring Workflow
1. Analysis Phase
a) Run detection tools in parallel
b) Collect all findings
c) Categorize by risk level:
- SAFE: Unused exports, unused dependencies
- CAREFUL: Potentially used via dynamic imports
- RISKY: Public API, shared utilities
2. Risk Assessment
For each item to remove:
- Check if it's imported anywhere (grep search)
- Verify no dynamic imports (grep for string patterns)
- Check if it's part of public API
- Review git history for context
- Test impact on build/tests
3. Safe Removal Process
a) Start with SAFE items only
b) Remove one category at a time:
1. Unused npm dependencies
2. Unused internal exports
3. Unused files
4. Duplicate code
c) Run tests after each batch
d) Create git commit for each batch
4. Duplicate Consolidation
a) Find duplicate components/utilities
b) Choose the best implementation:
- Most feature-complete
- Best tested
- Most recently used
c) Update all imports to use chosen version
d) Delete duplicates
e) Verify tests still pass
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 · 308 lines · 51 tokens per session scan A c300c2bcd344
refactor-cleaner is an agent published in the GitHub repository vibeeval/vibecosystem (541 stars, last pushed 2mo ago), licensed MIT. It adds 51 tokens to every session and 1,915 once invoked, about $0.0002 per session on Opus 5.5. 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-09-03.
Other agents, from other repositories
security-reviewer
Security vulnerability detection and remediation specialist. Use PROACTIVELY after writing code that handles user input, authentication, API endpoints, or sensitive data. Flags secrets, SSRF, injection, unsafe crypto, and OWASP Top 10 vulnerabilities.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
predictive-analyst
Precognition agent. Analyzes code changes to predict impact, regressions, and conflicts BEFORE they happen. Uses dependency graphs and historical data.
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
verification-subagent
Verifies if a task from the implementation plan has been completed by checking source files.
verifier
Verification agent for /craft:research-verify. Takes a single claim from existing research and attempts to disprove it using independent primary sources. Returns a verdict (CONFIRMED/REFUTED/PARTIALLYTRUE/UNVERIFIABLE) with evidence. NOT a researcher. Does not discover new topics or cast a wide net. Takes one claim…