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/fmarzochi/egc/refactor-cleangit clone --depth 1 https://github.com/Fmarzochi/EGCWrote 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/fmarzochi/egc/refactor-clean)<a href="https://agentmods.dev/commands/fmarzochi/egc/refactor-clean"><img src="https://agentmods.dev/badge/commands/fmarzochi/egc/refactor-clean.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.00006 | $0.00508 |
| Opus 5 | $0.00003 | $0.00254 |
| Sonnet 5 | $0.00001 | $0.00102 |
| Haiku 4.5 | $0.00001 | $0.00051 |
Grade A, and why
refactor-clean 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 yesterday.
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
97% identical to refactor-clean — 2 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactor Clean Command
Analyze and clean up the codebase: $ARGUMENTS
Your Task
- Detect dead code using analysis tools
- Identify duplicates and consolidation opportunities
- Safely remove unused code with documentation
- Verify no functionality broken
Detection Phase
Run Analysis Tools
# Find unused exports
npx knip
# Find unused dependencies
npx depcheck
# Find unused TypeScript exports
npx ts-prune
Manual Checks
- Unused functions (no callers)
- Unused variables
- Unused imports
- Commented-out code
- Unreachable code
- Unused CSS classes
Removal Phase
Before Removing
- Search for usage - grep, find references
- Check exports - might be used externally
- Verify tests - no test depends on it
- Document removal - git commit message
Safe Removal Order
- Remove unused imports first
- Remove unused private functions
- Remove unused exported functions
- Remove unused types/interfaces
- Remove unused files
Consolidation Phase
Identify Duplicates
- Similar functions with minor differences
- Copy-pasted code blocks
- Repeated patterns
Consolidation Strategies
- Extract utility function - for repeated logic
- Create base class - for similar classes
- Use higher-order functions - for repeated patterns
- Create shared constants - for magic values
Verification
After cleanup:
npm run build- builds successfullynpm test- all tests passnpm run lint- no new lint errors- Manual smoke test - features work
Report Format
Dead Code Analysis
==================
Removed:
- file.ts: functionName (unused export)
- utils.ts: helperFunction (no callers)
Consolidated:
- formatDate() and formatDateTime() → dateUtils.format()
Remaining (manual review needed):
- oldComponent.tsx: potentially unused, verify with team
CAUTION: Always verify before removing. When in doubt, ask or add // TODO: verify usage comment.
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.
- yesterday First seen · 103 lines · 6 tokens per session scan A 65f13b5cd807
refactor-clean is a command published in the GitHub repository Fmarzochi/EGC (48 stars, last pushed today), licensed Apache-2.0. It adds 6 tokens to every session and 508 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to refactor-clean, differing in 2 lines, and is treated as a copy.
Other commands, from other repositories
demand-discovery
Run automated niche demand discovery research across 7 data sources and 26 categories.
tdd-workflow
Implement the behavior described in $ARGUMENTS using strict TDD. Follow this exact sequence. Do not collapse phases. Each gate requires actual test runner output.
api-add-endpoint
Create a new API endpoint. $ARGUMENTS should describe the endpoint (e.g., "POST /api/users - create a user").
api-test-endpoint
Test the API endpoint specified in $ARGUMENTS.
code-review
Review the code changes in this project. For each file changed.
refactor-file
Refactor the file specified in $ARGUMENTS following project conventions.