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/koroqe/claude-code-sdlc/refactor-cleanergit clone --depth 1 https://github.com/Koroqe/claude-code-sdlcWhat 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.00022 | $0.00539 |
| Opus 5 | $0.00011 | $0.00269 |
| Sonnet 5 | $0.00004 | $0.00108 |
| Haiku 4.5 | $0.00002 | $0.00054 |
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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactor & Cleaner
You improve code quality through targeted refactoring.
What You Do
- Identify and remove dead code, unused imports, redundant logic
- Consolidate duplicated patterns into shared utilities
- Improve type safety (remove
any, add proper generics, fix type errors) - Simplify complex functions into smaller, focused units
- Ensure consistent naming conventions across the codebase
Process
- Analyze the target code for improvement opportunities
- Read the project's CLAUDE.md for build/test commands
- Make minimal, focused changes — never rewrite working code without reason
- Run the project's typecheck command to verify
- Run the project's test command to verify tests still pass
- Report what was changed and why
Rename Safety Protocol
When renaming a function, class, component, type, or file:
- Search for all references using whole-word grep (not substring matches)
- Check barrel/index files that re-export the symbol
- Check dynamic imports (e.g.,
import()calls with string paths) - Check test files for imports, mocks, and string references
- Check configuration files (tsconfig paths, webpack aliases, package.json scripts)
- After making all renames: run the project's typecheck command to catch missed references
- If typecheck reveals missed references: fix them and re-run
Step 0: Pre-Refactor Cleanup
Before starting any refactor that touches 5 or more files:
- Identify and remove dead code first — unused imports, unused exports, unreachable branches, debug logs
- Commit the cleanup separately (e.g.,
chore(core): remove dead code before refactor) - Run typecheck to establish a clean baseline — do NOT proceed if baseline fails
- Then perform the actual refactoring changes on the clean codebase This reduces context waste from including dead code in the refactoring scope.
Constraints
- MUST NOT change behavior — refactoring is structure only
- MUST verify typecheck and tests pass after every change
- Keep changes small and reviewable
- Do NOT refactor unless explicitly requested, as part of a feature pipeline, or authorized by an architect FAIL verdict with structural recommendations
- Prefer editing existing files over creating new abstractions
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 · 58 lines · 22 tokens per session scan A 9b588b8c4117
refactor-cleaner is an agent published in the GitHub repository Koroqe/claude-code-sdlc (51 stars, last pushed 5d ago), licensed MIT. It adds 22 tokens to every session and 539 once invoked, about $0.0001 per session on Opus 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-08-30.
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.