What is dotnet-upgrade?

A collection of prompts for assessing and carrying out upgrades to .NET projects. It examines project types, target frameworks, dependencies, legacy package formats, upgrade order, and rollback checkpoints.

Use it to classify projects, check dependency compatibility, detect packages.config projects, choose an incremental upgrade strategy, and track build, test, and deployment readiness.

It helps teams understand upgrade complexity and organize the work so dependent projects are updated in a safer order.

dotnet-upgrade — Skill for Claude Code and Codex by OKHP3

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 OKHP3/skillz --skill dotnet-upgrade

Clone the repo

git clone --depth 1 https://github.com/OKHP3/skillz

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/okhp3/skillz/dotnet-upgrade.svg)](https://agentmods.dev/skills/okhp3/skillz/dotnet-upgrade)

Your own site

<a href="https://agentmods.dev/skills/okhp3/skillz/dotnet-upgrade"><img src="https://agentmods.dev/badge/skills/okhp3/skillz/dotnet-upgrade.svg" alt="Measured on agentmods" height="20"></a>

Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,327 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 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.

Model	Per session	Once invoked
Fable 5.1	$0.00018	$0.01327
Opus 5	$0.00009	$0.00664
Sonnet 5	$0.00004	$0.00265
Haiku 4.5	$0.00002	$0.00133

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

Security

Grade A, and why

dotnet-upgrade 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 4d 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 dotnet-upgrade — 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.

community/dotnet-upgrade/SKILL.md · 117 lines

How it starts

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

Project Discovery & Assessment

name: "Project Classification Analysis" prompt: "Identify all projects in the solution and classify them by type (.NET Framework, .NET Core, .NET Standard). Analyze each .csproj for its current TargetFramework and SDK usage."
name: "Dependency Compatibility Review" prompt: "Review external and internal dependencies for framework compatibility. Determine the upgrade complexity based on dependency graph depth."
name: "Legacy Package Detection" prompt: "Identify legacy packages.config projects needing migration to PackageReference format."

Upgrade Strategy & Sequencing

name: "Project Upgrade Ordering" prompt: "Recommend a project upgrade order from least to most dependent components. Suggest how to isolate class library upgrades before API or Azure Function migrations."
name: "Incremental Strategy Planning" prompt: "Propose an incremental upgrade strategy with rollback checkpoints. Evaluate the use of Upgrade Assistant or manual upgrades based on project structure."
name: "Progress Tracking Setup" prompt: "Generate an upgrade checklist for tracking build, test, and deployment readiness across all projects."

Framework Targeting & Code Adjustments

name: "Target Framework Selection" prompt: "Suggest the correct TargetFramework for each project (e.g., net8.0). Review and update deprecated SDK or build configurations."
name: "Code Modernization Analysis" prompt: "Identify code patterns needing modernization (e.g., WebHostBuilder → HostBuilder). Suggest replacements for deprecated .NET APIs and third-party libraries."
name: "Async Pattern Conversion" prompt: "Recommend conversion of synchronous calls to async where appropriate for improved performance and scalability."

NuGet & Dependency Management

name: "Package Compatibility Analysis" prompt: "Analyze outdated or incompatible NuGet packages and suggest compatible versions. Identify third-party libraries that lack .NET 8 support and provide migration paths."
name: "Shared Dependency Strategy" prompt: "Recommend strategies for handling shared dependency upgrades across projects. Evaluate usage of legacy packages and suggest alternatives in Microsoft-supported namespaces."
name: "Transitive Dependency Review" prompt: "Review transitive dependencies and potential version conflicts after upgrade. Suggest resolution strategies for dependency conflicts."

CI/CD & Build Pipeline Updates

name: "Pipeline Configuration Analysis" prompt: "Analyze YAML build definitions for SDK version pinning and recommend updates. Suggest modifications for UseDotNet@2 and NuGetToolInstaller tasks."
name: "Build Pipeline Modernization" prompt: "Generate updated build pipeline snippets for .NET 8 migration. Recommend validation builds on feature branches before merging to main."
name: "CI Automation Enhancement" prompt: "Identify opportunities to automate test and build verification in CI pipelines. Suggest strategies for continuous integration validation."

Testing & Validation

name: "Build Validation Strategy" prompt: "Propose validation checks to ensure the upgraded solution builds and runs successfully. Recommend automated test execution for unit and integration suites post-upgrade."
name: "Service Integration Verification" prompt: "Generate validation steps to verify logging, telemetry, and service connectivity. Suggest strategies for verifying backward compatibility and runtime behavior."
name: "Deployment Readiness Check" prompt: "Recommend UAT deployment verification steps before production rollout. Create comprehensive testing scenarios for upgraded components."

Breaking Change Analysis

name: "API Deprecation Detection" prompt: "Identify deprecated APIs or removed namespaces between target versions. Suggest automated scanning using .NET Upgrade Assistant and API Analyzer."

Read the full file on GitHub · 117 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.

4d ago First seen · 117 lines · 18 tokens per session scan A 9e3e789579cc

Subscribe to this mod's changes

dotnet-upgrade is a skill published in the GitHub repository OKHP3/skillz (3 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 1,327 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to dotnet-upgrade, differing in 0 lines, and is treated as a copy.

C# and .NET Languages Planning agent-skills claude-skills linkedin mermaid openclaw-skills skill-md

csharp-developer

Use when building C# applications with .NET 8+, ASP.NET Core APIs, or Blazor web apps. Builds REST APIs using minimal or controller-based routing, configures database access with Entity Framework Core, implements async patterns and cancellation, structures applications with CQRS via MediatR, and scaffolds Blazor…

Jeffallan/claude-skills · 102 tokens

dotnet-core-expert

Use when building .NET 8 applications with minimal APIs, clean architecture, or cloud-native microservices. Invoke for Entity Framework Core, CQRS with MediatR, JWT authentication, AOT compilation.

Jeffallan/claude-skills · 47 tokens

eplan-development

Develop EPLAN Electric P8 scripts, API extensions, and remote-control applications. Use when writing C# scripts for EPLAN (actions, event handlers, ribbon), accessing the EPLAN API (parts database, projects, pages), building external apps that drive EPLAN via Remote Client, or debugging EPLAN automation issues…

covagashi/eplan-rag-mcp · 84 tokens

dotnet-upgrade