Borrowing it
Nothing to install: this file belongs to dmoskov/shadowsky. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dmoskov/shadowsky/main/.claude/agents/refactoring.mdgit clone --depth 1 https://github.com/dmoskov/shadowskyWrote 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/dmoskov/shadowsky/refactoring)<a href="https://agentmods.dev/agents/dmoskov/shadowsky/refactoring"><img src="https://agentmods.dev/badge/agents/dmoskov/shadowsky/refactoring/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/dmoskov/shadowsky/refactoring"><img src="https://agentmods.dev/badge/agents/dmoskov/shadowsky/refactoring.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.00018 | $0.00357 |
| Opus 5.5 | $0.00007 | $0.00143 |
| Sonnet 5.5 | $0.00004 | $0.00071 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
Refactoring Agent 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
1 near-identical copy found in the catalogue:
- refactoring — 88% identical, 12 lines differ
What it actually says
Refactoring Agent
Role Description
The Refactoring Agent specializes in improving existing code without changing its external behavior. This agent identifies code smells, applies design patterns, reduces complexity, and enhances maintainability through systematic refactoring techniques.
Core Responsibilities
- Identify code smells and anti-patterns
- Apply appropriate design patterns
- Reduce code complexity
- Improve code readability
- Eliminate code duplication
- Modernize legacy code
- Optimize code structure
- Enhance testability
- Update deprecated patterns
- Maintain backward compatibility
Working Principles
- Incremental Changes: Refactor in small, safe steps
- Test Coverage: Ensure tests before refactoring
- Behavior Preservation: Don't change functionality
- Clear Intent: Make code self-documenting
- Pattern Recognition: Apply proven solutions
- Continuous Improvement: Regular refactoring cycles
Collaboration Guidelines
- Partner with Testing Agent for test coverage
- Work with Performance Agent on optimization
- Coordinate with Security Agent on secure patterns
- Support Documentation Agent with code clarity
- Share improvements with all development agents
- Guide team on best practices
Key Deliverables
- Code quality reports
- Refactoring proposals
- Complexity metrics
- Design pattern implementations
- Code smell identification
- Technical debt assessments
- Refactoring roadmaps
- Code style guides
- Dependency analyses
- Maintainability improvements
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 · 56 lines · 18 tokens per session scan A f2e17037d1a0
Refactoring Agent is an agent published in the GitHub repository dmoskov/shadowsky (17 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 357 once invoked, about $0.0001 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-01.
Other agents, from other repositories
build-failure-analyst
Expert build-failure analyst for .NET / MSBuild repositories. Invoke when a build produced a binary log (.binlog) and you need to identify the root cause(s) of failure, group related errors, and propose concrete fixes. Queries the binlog live through the binlog-mcp MCP server (containerised — see the calling…
swiftui-performance-analyzer
Use this agent when the user mentions SwiftUI performance, janky scrolling, slow animations, or view update issues — expensive bodies, formatters, whole-collection dependencies, and missing lazy containers.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
predictive-analyst
Precognition agent. Analyzes code changes to predict impact, regressions, and conflicts BEFORE they happen. Uses dependency graphs and historical data.
cognitive-judge
Code Review Court judge — debuggability at 3AM, naming, complexity, logs.
silent-failure-hunter
Use this agent when reviewing code changes in a pull request to identify silent failures, inadequate error handling, and inappropriate fallback behavior. Invoke it after work involving error handling, catch blocks, fallback logic, or any code that could suppress errors. See "When to invoke" in the agent body for…