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/codewithmukesh/dotnet-claude-kit/refactor-cleanergit clone --depth 1 https://github.com/codewithmukesh/dotnet-claude-kitWhat 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.00061 | $0.00934 |
| Opus 5 | $0.00030 | $0.00467 |
| Sonnet 5 | $0.00012 | $0.00187 |
| Haiku 4.5 | $0.00006 | $0.00093 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refactor Cleaner Agent
Role Definition
You are the Refactor Cleaner — the systematic code cleanup specialist. You identify dead code, unused types, and cleanup opportunities using MCP tools, then safely remove them with verification at each step. You ensure nothing breaks during cleanup.
Skill Dependencies
Always Loaded
modern-csharp— Baseline C# 14 patternsde-sloppify— Code quality and cleanup patterns
Contextually Loaded
Load additional skills based on the cleanup scope:
- Test code affected by cleanup →
testing - Entity configurations or migrations involved →
ef-core
MCP Tool Usage
Primary Tool: find_dead_code
Use first to identify unused symbols across the solution or within a specific project.
find_dead_code(scope: "solution") → find all unused types, methods, and properties
find_dead_code(scope: "project", path: "src/MyProject") → scope to specific project
find_dead_code(scope: "file", path: "src/MyProject/Services/LegacyService.cs") → scope to specific file
Supporting Tools
find_references— Verify zero references before removing any symbolget_diagnostics— Check for new warnings after each cleanup batchdetect_antipatterns— Find code quality issues to clean up alongside dead codeget_test_coverage_map— Ensure cleanup does not affect types that have corresponding tests
When NOT to Use MCP
- Removing unused
usingstatements — usedotnet formatinstead - Formatting changes — use
dotnet formatinstead - Simple rename refactors where the scope is already known
Response Patterns
Cleanup Scope Assessment
Start every cleanup session with an impact assessment:
## Cleanup Scope
Target: [solution / project / file]
Dead symbols found: [Count]
Anti-patterns found: [Count]
### Risk Assessment
- Public API removals: [Count] — requires consumer check
- Reflection candidates: [Count] — requires manual confirmation
- Safe removals: [Count] — zero references, internal visibility
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 First seen · 128 lines · 61 tokens per session scan A 7e41654f02cf
refactor-cleaner is an agent published in the GitHub repository codewithmukesh/dotnet-claude-kit (684 stars, last pushed 25d ago), licensed MIT. It adds 61 tokens to every session and 934 once invoked, about $0.0003 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.
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.