migrate-package

migrate-package is a skill for Claude Code from darylmcd/Roslyn-Backed-MCP. It costs 47 tokens per session (1,419 once invoked), scanned A, original, MIT.

A .NET dependency migration helper for changing NuGet packages, which are reusable libraries used by .NET projects. It takes an old package, a replacement package, and a target version, then guides the change across a solution.

In plain words
What is it for?
Use it to replace a NuGet package across a .NET solution, upgrade a package, or move away from a deprecated package.
Why use it?
It helps find every project using the old package and checks package versions and known security issues before the migration. This reduces missed references and unsafe upgrades.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Part of the roslyn-mcp plugin — 44 skills, 5 agents, 2 hooks, 2 MCP servers shipped together

Good fit Use it to replace a NuGet package across a .NET solution, upgrade a package, or move away from a deprecated package.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/darylmcd/roslyn-backed-mcp/migrate-package
Install

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.

Any agent
npx skills add darylmcd/Roslyn-Backed-MCP --skill migrate-package
Clone the repo
git clone --depth 1 https://github.com/darylmcd/Roslyn-Backed-MCP

Made for: Claude Code.

Or install roslyn-mcp, the plugin that ships this one along with the rest of its 44 skills, 5 agents, 2 hooks, 2 MCP servers.

Wrote 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.

agentmods badge for migrate-package

README.md
[![agentmods](https://agentmods.dev/badge/skills/darylmcd/roslyn-backed-mcp/migrate-package/github.svg)](https://agentmods.dev/skills/darylmcd/roslyn-backed-mcp/migrate-package)
Your own site
<a href="https://agentmods.dev/skills/darylmcd/roslyn-backed-mcp/migrate-package"><img src="https://agentmods.dev/badge/skills/darylmcd/roslyn-backed-mcp/migrate-package/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.

agentmods 80×15 button for migrate-package

Your own site · 80×15
<a href="https://agentmods.dev/skills/darylmcd/roslyn-backed-mcp/migrate-package"><img src="https://agentmods.dev/badge/skills/darylmcd/roslyn-backed-mcp/migrate-package.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,419 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00047 $0.01419
Opus 5 $0.00023 $0.00709
Sonnet 5 $0.00009 $0.00284
Haiku 4.5 $0.00005 $0.00142

Measured 9d ago against content hash 42566300c6a0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

migrate-package 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 9d 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.

skills/migrate-package/SKILL.md · 124 lines

How it starts

The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.

NuGet Package Migration

You are a .NET dependency management specialist. Your job is to safely migrate NuGet package references across a solution using Roslyn's orchestrated preview/apply workflow.

Input

$ARGUMENTS should contain three values: <old-package> <new-package> <new-version>

Examples:

  • Newtonsoft.Json System.Text.Json 9.0.0
  • Microsoft.Extensions.Logging.Abstractions Microsoft.Extensions.Logging.Abstractions 10.0.0
  • Moq NSubstitute 5.0.0

If the user provides incomplete arguments, ask for the missing values.

Server discovery

Use discover_capabilities (project-mutation / all) or guided_package_migration MCP prompt with the same package ids and version.

Workflow

Step 1: Audit Current State

  1. Ensure a workspace is loaded.
  2. Call get_nuget_dependencies to list all package references.
  3. Find the old package: which projects reference it, at what versions.
  4. If the old package is not found, report this and stop.

Step 2: Vulnerability Check

  1. Call nuget_vulnerability_scan to check if either package has known CVEs.
  2. Report any vulnerabilities in the current version.
  3. Confirm the new version does not have known vulnerabilities.

Step 3: Preview Migration

  1. Call migrate_package_preview with:
    • oldPackageId: the package to replace
    • newPackageId: the replacement package
    • newVersion: the target version
  2. Show the preview:
    • Number of projects affected
    • Package reference changes in each .csproj
    • Any version conflicts

Step 4: Apply Migration

After user confirmation:

  1. Call apply_composite_preview with the preview token.
  2. Call compile_check to verify the solution still compiles.
  3. If compilation fails:
    • Call project_diagnostics to identify breaking changes.
    • Report errors with file locations and suggested fixes.
    • Note that API differences between old and new packages may require code changes.

Step 5: Post-Migration Verification

  1. Call compile_check for a final verification.
  2. If there are test projects, suggest running test_run to verify behavior.
  3. Call get_nuget_dependencies again to confirm the migration is reflected.

Read the full file on GitHub · 124 lines

Changes

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.

  1. 9d ago First seen · 124 lines · 47 tokens per session scan A 42566300c6a0

Subscribe to this mod's changes

migrate-package is a skill published in the GitHub repository darylmcd/Roslyn-Backed-MCP (1 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 1,419 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.

Related

Other skills, from other repositories

git-workflow-and-versioning

Structures git workflow practices for .NET/C# projects — atomic commits, trunk-based branches, pre-commit hygiene with dotnet test + dotnet format, worktrees for parallel agent work. Use when making any code change to a .NET solution, when committing, branching, resolving conflicts, or organizing work across multiple…

peterblazejewicz/claude-plugins · 76 tokens

build-and-test

How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.

microsoft/agent-framework · 26 tokens

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.

zhaoxuya520/reverse-skill · 144 tokens

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…

ag-ui-protocol/ag-ui · 223 tokens

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…

microsoft/skills · 97 tokens

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…

dotnet/skills · 149 tokens