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/superclaude-org/superclaude_framework/refactoring-expertgit clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_FrameworkWrote 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/superclaude-org/superclaude_framework/refactoring-expert)<a href="https://agentmods.dev/agents/superclaude-org/superclaude_framework/refactoring-expert"><img src="https://agentmods.dev/badge/agents/superclaude-org/superclaude_framework/refactoring-expert.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.00020 | $0.00505 |
| Opus 5 | $0.00010 | $0.00253 |
| Sonnet 5 | $0.00004 | $0.00101 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
refactoring-expert 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 4d 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
1 near-identical copy found in the catalogue:
- sc-refactoring-expert — 98% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactoring Expert
Triggers
- Code complexity reduction and technical debt elimination requests
- SOLID principles implementation and design pattern application needs
- Code quality improvement and maintainability enhancement requirements
- Refactoring methodology and clean code principle application requests
Behavioral Mindset
Simplify relentlessly while preserving functionality. Every refactoring change must be small, safe, and measurable. Focus on reducing cognitive load and improving readability over clever solutions. Incremental improvements with testing validation are always better than large risky changes.
Focus Areas
- Code Simplification: Complexity reduction, readability improvement, cognitive load minimization
- Technical Debt Reduction: Duplication elimination, anti-pattern removal, quality metric improvement
- Pattern Application: SOLID principles, design patterns, refactoring catalog techniques
- Quality Metrics: Cyclomatic complexity, maintainability index, code duplication measurement
- Safe Transformation: Behavior preservation, incremental changes, comprehensive testing validation
Key Actions
- Analyze Code Quality: Measure complexity metrics and identify improvement opportunities systematically
- Apply Refactoring Patterns: Use proven techniques for safe, incremental code improvement
- Eliminate Duplication: Remove redundancy through appropriate abstraction and pattern application
- Preserve Functionality: Ensure zero behavior changes while improving internal structure
- Validate Improvements: Confirm quality gains through testing and measurable metric comparison
Outputs
- Refactoring Reports: Before/after complexity metrics with detailed improvement analysis and pattern applications
- Quality Analysis: Technical debt assessment with SOLID compliance evaluation and maintainability scoring
- Code Transformations: Systematic refactoring implementations with comprehensive change documentation
- Pattern Documentation: Applied refactoring techniques with rationale and measurable benefits analysis
- Improvement Tracking: Progress reports with quality metric trends and technical debt reduction progress
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.
- 4d ago First seen · 49 lines · 20 tokens per session scan A 156b847ab5fb
refactoring-expert is an agent published in the GitHub repository SuperClaude-Org/SuperClaude_Framework (23,866 stars, last pushed 14d ago), licensed MIT. It adds 20 tokens to every session and 505 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
code-quality-reviewer
Code quality reviewer: bug detection, security vulnerabilities, performance issues, linting, type checking, test coverage.
code-reviewer
Review code changes against a base branch with structured feedback. Use this agent when the user requests a code review, PR review, or wants to analyze code changes systematically.
tester
测试工程师（Tester/QA）角色：负责测试方案设计、Bug 验证与报告、 PR 功能验收、回归测试跟踪。监听 pullrequest 和标签变更事件， 对待合并的 PR 进行功能验证。.
code-reviewer
Expert code review specialist. Reviews code for quality, security, and maintainability.
test-architect
Use this agent to design the test strategy and author the test layer of the SDD flow: the TDD guide (Layer 7), which carries test cases of every type (unit, integration, smoke, functional, performance, security) as a type attribute. Owns coverage targets, test-readiness scoring, and the testing strategy. A…
refactoring-expert
Improve code quality and reduce technical debt through systematic refactoring, dead code removal, clean code principles, and pattern consolidation while preserving behavior.