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.
git clone --depth 1 https://github.com/dmoskov/sharedskillsWrote 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/sharedskills/refactoring)<a href="https://agentmods.dev/agents/dmoskov/sharedskills/refactoring"><img src="https://agentmods.dev/badge/agents/dmoskov/sharedskills/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/sharedskills/refactoring"><img src="https://agentmods.dev/badge/agents/dmoskov/sharedskills/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.00024 | $0.00344 |
| Opus 5.5 | $0.00010 | $0.00138 |
| Sonnet 5.5 | $0.00005 | $0.00069 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
refactoring 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 2mo 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.
This is a copy
88% identical to Refactoring Agent — 12 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.
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.
- 2mo ago First seen · 50 lines · 24 tokens per session scan A a7cf69fc9b05
refactoring is an agent published in the GitHub repository dmoskov/sharedskills (2 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 344 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to Refactoring Agent, differing in 12 lines, and is treated as a copy.
Other agents, from other repositories
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.