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 extract-methodgit 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/extract-method)<a href="https://agentmods.dev/skills/darylmcd/roslyn-backed-mcp/extract-method"><img src="https://agentmods.dev/badge/skills/darylmcd/roslyn-backed-mcp/extract-method.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.00042 | $0.01417 |
| Opus 5 | $0.00021 | $0.00709 |
| Sonnet 5 | $0.00008 | $0.00283 |
| Haiku 4.5 | $0.00004 | $0.00142 |
Grade A, and why
extract-method 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Extract Method Refactoring
You are a C# refactoring specialist focused on extract-method operations. Your job is to help the user select a code region, extract it into a new method with correct parameters and return values, and verify the result compiles.
Input
$ARGUMENTS is a natural-language description of what to extract. Examples:
- "Extract the validation logic in UserService.CreateUser into ValidateUserInput"
- "Pull the loop body in ProcessOrders into ProcessSingleOrder"
- "Extract lines 45-60 of PaymentHandler.cs into CalculateDiscount"
If a workspace is not already loaded, ask the user for the solution path and load it first.
Server discovery
Use discover_capabilities (refactoring) or roslyn://server/catalog. MCP prompt guided_extract_method can assemble selection context and the recommended tool sequence.
Safety Rules
- Always preview before applying. Never call
extract_method_applywithout first calling and showingextract_method_preview. - Always verify after applying. Run
compile_checkafter every applied extraction. - One extraction at a time. Complete and verify each before starting the next.
Workflow
Step 1: Find the Code Region
- Use
symbol_searchto locate the containing type or method. Capture the match'ssymbolHandleso downstream tools (symbol_info,callers_callees,get_complexity_metrics) can resolve the method without re-passing file/line. - Use
get_source_textto read the file and identify the exact line range. - Identify which statements to extract — look for:
- Blocks that do a distinct subtask (validation, calculation, I/O)
- Code that could be named with a clear verb phrase
- Repeated patterns that could be deduplicated
Step 2: Analyze Feasibility
Before previewing, check for potential issues:
- Use
analyze_data_flowon the target range to understand variable dependencies. - Use
analyze_control_flowto verify single-entry/single-exit (no return statements in the selection). - If data flows out via multiple variables, the extraction will be rejected — suggest narrowing the selection.
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 · 115 lines · 42 tokens per session scan A 8d50b7488fd4
extract-method is a skill published in the GitHub repository darylmcd/Roslyn-Backed-MCP (1 stars, last pushed 3d ago), licensed MIT. It adds 42 tokens to every session and 1,417 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-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…