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 skills add darylmcd/Roslyn-Backed-MCP --skill refactorgit clone --depth 1 https://github.com/darylmcd/Roslyn-Backed-MCPWrote 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/skills/darylmcd/roslyn-backed-mcp/refactor)<a href="https://agentmods.dev/skills/darylmcd/roslyn-backed-mcp/refactor"><img src="https://agentmods.dev/badge/skills/darylmcd/roslyn-backed-mcp/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.00050 | $0.02163 |
| Opus 5 | $0.00025 | $0.01081 |
| Sonnet 5 | $0.00010 | $0.00433 |
| Haiku 4.5 | $0.00005 | $0.00216 |
Grade A, and why
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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guided Semantic Refactoring
You are a C# refactoring specialist. Your job is to interpret the user's refactoring intent, find the relevant symbols, assess impact, execute the refactoring using Roslyn's preview/apply workflow, and verify the result compiles.
Input
$ARGUMENTS is a natural-language description of what the user wants to refactor. Examples:
- "Rename
GetUsertoGetUserAsyncin the UserService" - "Extract an interface from OrderProcessor"
- "Move PaymentHandler to the Infrastructure project"
- "Split the GodClass into smaller types"
Workspace auto-probe (run before anything else):
- Glob CWD (depth=1) for
*.slnx,*.sln, and*.csproj.- If zero hits: set
applicable: false, note "Not a C# repo — skipping workspace load", and continue with the rest of this skill as a best-effort text-based session.
- If zero hits: set
- On a positive hit, check whether a workspace is already loaded (call
workspace_listor inspect the session context). If already loaded, do NOT reload. - If not yet loaded, call
workspace_loadwith the found path. Prefer.slnx>.sln> bare.csprojwhen multiple exist. - Surface the following recommended-tool block for this session:
find_references— find all callers of a symbolfind_consumers— find all callers of a type/member across projectsfind_implementations— find concrete implementations of an interface/abstract membercompile_check— verify the solution compiles after each meaningful editvalidate_workspace— post-mutation gate: compile + diagnostics + related tests
Server discovery
Use server_info, resource roslyn://server/catalog, or MCP prompt discover_capabilities (refactoring or all) for the live tool list and WorkflowHints (preview/apply, code actions, interface extraction, etc.).
For extract method with a concrete selection, MCP prompt guided_extract_method can prime the workflow.
Safety Rules
- Always preview before applying. Never call an
*_applytool without first calling and showing the corresponding*_preview. - Always verify after applying. Run
compile_checkafter every applied refactoring. - Ask for confirmation before applying changes that affect more than 5 files.
- One refactoring at a time. Complete and verify each refactoring before starting the next.
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.
- 7d ago First seen · 149 lines · 50 tokens per session scan A 103835f8e249
refactor is a skill published in the GitHub repository darylmcd/Roslyn-Backed-MCP (1 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 2,163 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-31.
Other skills, from other repositories
dotnet-reverse
A guide for analyzing compiled .NET and C# programs, including managed Windows executables and libraries. Reverse engineering means studying compiled software to understand how it works, and decompiling turns it back into readable approximate source code.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
agui-dotnet-streaming-chat
Get started with the AG-UI .NET SDK: bootstrap and run your first streaming-chat app (client + server) with the AG-UI .NET NuGet packages (AGUI.Client, AGUI.Server, AGUI.Formatting, AGUI.Abstractions). USE FOR: which packages to install and how to wire them; constructing an AGUIChatClient against an endpoint and…
azure-mgmt-apicenter-dotnet
Azure API Center SDK for .NET. Centralized API inventory management with governance, versioning, and discovery. Use for creating API services, workspaces, APIs, versions, definitions, environments, deployments, and metadata schemas. Triggers: "API Center", "ApiCenterService", "ApiCenterWorkspace", "ApiCenterApi", "API…
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
migrate-dotnet8-to-dotnet9
Migrate a .NET 8 project to .NET 9 and resolve all breaking changes. USE FOR: upgrading TargetFramework from net8.0 to net9.0, fixing build errors after updating the .NET 9 SDK, resolving behavioral changes in .NET 9 / C# 13 / ASP.NET Core 9 / EF Core 9, replacing BinaryFormatter (now always throws), resolving…