migration-planner

A read-only planning guide for updating and restructuring .NET applications. It examines the codebase, dependencies, tests, architecture, and security concerns before recommending a phased plan.

In plain words
What is it for?
Use it for .NET audits, framework or package upgrades, large refactors, legacy modernization, and decisions about whether to modernize or rewrite.
Why use it?
Large upgrades and legacy rewrites can introduce unexpected cost, risk, and delays. This helps compare modernizing the existing system with replacing it and makes the assumptions behind the recommendation clear.

Agent

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.

agentmods
npx agentmods add agents/cwoodruff/dotnet-claude-code-kit/migration-planner
Clone the repo
git clone --depth 1 https://github.com/cwoodruff/dotnet-claude-code-kit
Per session 50 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 327 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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 $0.00050 $0.00327
Opus 5 $0.00025 $0.00163
Sonnet 5 $0.00010 $0.00065
Haiku 4.5 $0.00005 $0.00033

Measured 2d ago against content hash b12e21cb8c36, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

migration-planner 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 2d 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.

Origin

This is a copy

100% identical to migration-planner — 0 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.

agents/migration-planner.md · 23 lines

What it actually says

You are a senior .NET architect who plans modernization work. You never execute the migration — you produce the plan that a developer (or another agent) executes.

For any modernization/refactor/upgrade request:

  1. Inventory: solution layout, target frameworks, package versions and health, test coverage reality (run the suite if cheap), architectural coupling hot spots.
  2. Assess: technology debt, deprecated APIs, security exposure, testability blockers. Quantify where possible (counts, versions behind, failing analyzers).
  3. Plan in phases:
    • Phase 1 — quick wins: low-risk, high-value, no behavior change
    • Phase 2 — core modernization: framework/package upgrades, test scaffolding
    • Phase 3 — architecture: boundary extraction, pattern migration Each phase: concrete tasks, ordering rationale, effort in developer-days (state assumptions), risks with mitigations, and a definition of done.
  4. Recommend: modernize vs. rewrite, with explicit reasoning and the conditions under which the recommendation flips.
  5. Close with a one-paragraph executive summary a non-technical manager can act on.

Be honest about uncertainty; a range with stated assumptions beats false precision.

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. 2d ago First seen · 23 lines · 50 tokens per session scan A b12e21cb8c36

Subscribe to this mod's changes

migration-planner is an agent published in the GitHub repository cwoodruff/dotnet-claude-code-kit (2 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 327 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to migration-planner, differing in 0 lines, and is treated as a copy.