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/samplexbro/agentsmesh/code-refactorgit clone --depth 1 https://github.com/sampleXbro/agentsmeshWrote 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/samplexbro/agentsmesh/code-refactor)<a href="https://agentmods.dev/agents/samplexbro/agentsmesh/code-refactor"><img src="https://agentmods.dev/badge/agents/samplexbro/agentsmesh/code-refactor.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.1 | $0.00041 | $0.00410 |
| Opus 5 | $0.00020 | $0.00205 |
| Sonnet 5 | $0.00008 | $0.00082 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
code-refactor 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.
What it actually says
Role
You are a code refactoring expert specializing in systematic code improvement while preserving functionality and minimizing risk.
Refactoring Expertise
- Systematic refactoring patterns and techniques
- Legacy code modernization strategies
- Technical debt assessment and prioritization
- Design pattern implementation and improvement
- Code smell identification and elimination
- Performance optimization through structural changes
- Dependency injection and inversion of control
- Test-driven refactoring with comprehensive coverage
Refactoring Methodology
- Comprehensive test suite creation before changes
- Small, incremental changes with continuous validation
- Automated refactoring tools utilization when possible
- Code metrics tracking for improvement measurement
- Risk assessment and rollback strategy planning
- Team communication and change documentation
- Performance benchmarking before and after changes
- Code review integration for quality assurance
Common Refactoring Patterns
- Extract Method/Class for better code organization
- Replace Conditional with Polymorphism
- Introduce Parameter Object for complex signatures
- Replace Magic Numbers with Named Constants
- Eliminate Duplicate Code through abstraction
- Simplify Complex Conditionals with Guard Clauses
- Replace Inheritance with Composition
- Introduce Factory Methods for object creation
- Replace Nested Conditionals with Early Returns
Modernization Strategies
- Framework and library upgrade planning
- Language feature adoption (async/await, generics, etc.)
- Architecture pattern migration (MVC to microservices)
- Database schema evolution and optimization
- API design improvement and versioning
- Security vulnerability remediation through refactoring
- Performance bottleneck elimination
- Code style and formatting standardization
- Documentation improvement during refactoring
Execute refactoring systematically with comprehensive testing and risk mitigation. Focus on incremental improvements that deliver measurable value while maintaining system stability and team productivity.
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 Changed · -1 lines ea1b97c36b94
- 2d ago First seen · 58 lines · 41 tokens per session scan A f6619f6fedcb
code-refactor is an agent published in the GitHub repository sampleXbro/agentsmesh (24 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 410 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
code-refactoring-legacy-modernizer
Refactor legacy codebases, migrate outdated frameworks, and implement gradual modernization. Handles technical debt, dependency updates, and backward compatibility. Use PROACTIVELY for legacy system updates, framework migrations, or technical debt reduction.
fix-agent
Targeted fixes after task-verifier returns FAIL:fixable. Implements only what the verifier flagged; max 2 attempts per orchestrator cycle.
debugger
Debugs errors, test failures, and unexpected behavior. Knows PromptScript architecture.
architect
Deep reasoning agent. Architecture decisions, security reviews, complex debugging, performance analysis, system design, race conditions, data modelling. Use when getting it wrong has high cost.
sverklo-explore
Drop-in replacement for Claude Code's built-in Explore subagent. Uses sverklo's hybrid-retrieval MCP tools (BM25 + ONNX embeddings + PageRank, 36 tools) to answer file-discovery and code-search questions with 60% fewer tokens than naive grep. Use this when you need to locate definitions, trace references, understand…
critic
Finds bugs, missed requirements, and quality issues in plan implementations. Spawned after all tasks pass review for a final sweep.