.NET Upgrade

.NET Upgrade is an agent for coding agents from github/awesome-copilot. It costs 23 tokens per session (1,659 once invoked), scanned A, original, MIT.

A set of instructions for upgrading C# and .NET projects, including finding their current framework versions and planning moves to newer long-term-support releases. It also covers cleanup, modernization, dependency order, and breaking changes.

In plain words
What is it for?
Use it to inventory project target versions, plan an upgrade path, identify dependencies and breaking changes, modernize code, and create project-by-project upgrade steps.
Why use it?
It helps turn a broad framework upgrade into a sequence of smaller, understood changes. This reduces surprises when projects depend on one another or when newer .NET versions require code adjustments.

Agent

About the project

Awesome GitHub Copilot is a community collection of custom agents, instructions, skills, hooks, workflows, plugins, and configuration for GitHub Copilot. It helps Copilot users customize coding and development tasks. Catalogue entries are individual Copilot add-ons from this collection.

github/awesome-copilot · 38,647 stars · on GitHub

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/github/awesome-copilot/dotnet-upgrade
Clone the repo
git clone --depth 1 https://github.com/github/awesome-copilot

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 .NET Upgrade

README.md
[![agentmods](https://agentmods.dev/badge/agents/github/awesome-copilot/dotnet-upgrade.svg)](https://agentmods.dev/agents/github/awesome-copilot/dotnet-upgrade)
Your own site
<a href="https://agentmods.dev/agents/github/awesome-copilot/dotnet-upgrade"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/dotnet-upgrade.svg" alt="Measured on agentmods" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,659 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00023 $0.01659
Opus 5 $0.00012 $0.00830
Sonnet 5 $0.00005 $0.00332
Haiku 4.5 $0.00002 $0.00166

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

Security

Grade A, and why

.NET 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 yesterday.

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

Copies of this mod

2 near-identical copies found in the catalogue:

agents/dotnet-upgrade.agent.md · 224 lines

How it starts

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

.NET Upgrade Collection

.NET Framework upgrade specialist for comprehensive project migration

Tags: dotnet, upgrade, migration, framework, modernization

Collection Usage

.NET Upgrade Chat Mode

Discover and plan your .NET upgrade journey!

---
mode: dotnet-upgrade
title: Analyze current .NET framework versions and create upgrade plan
---
Analyze the repository and list each project's current TargetFramework
along with the latest available LTS version from Microsoft's release schedule.
Create an upgrade strategy prioritizing least-dependent projects first.

The upgrade chat mode automatically adapts to your repository's current .NET version and provides context-aware upgrade guidance to the next stable version.

It will help you:

  • Auto-detect current .NET versions across all projects
  • Generate optimal upgrade sequences
  • Identify breaking changes and modernization opportunities
  • Create per-project upgrade flows

.NET Upgrade Instructions

Execute comprehensive .NET framework upgrades with structured guidance!

The instructions provide:

  • Sequential upgrade strategies
  • Dependency analysis and sequencing
  • Framework targeting and code adjustments
  • NuGet and dependency management
  • CI/CD pipeline updates
  • Testing and validation procedures

Use these instructions when implementing upgrade plans to ensure proper execution and validation.


.NET Upgrade Prompts

Quick access to specialized upgrade analysis prompts!

The prompts collection includes ready-to-use queries for:

  • Project discovery and assessment
  • Upgrade strategy and sequencing
  • Framework targeting and code adjustments
  • Breaking change analysis
  • CI/CD pipeline updates
  • Final validation and delivery

Use these prompts for targeted analysis of specific upgrade aspects.


Quick Start

  1. Run a discovery pass to enumerate all *.sln and *.csproj files in the repository.
  2. Detect the current .NET version(s) used across projects.
  3. Identify the latest available stable .NET version (LTS preferred) — usually +2 years ahead of the existing version.
  4. Generate an upgrade plan to move from current → next stable version (e.g., net6.0 → net8.0, or net7.0 → net9.0).
  5. Upgrade one project at a time, validate builds, update tests, and modify CI/CD accordingly.

Read the full file on GitHub · 224 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. yesterday First seen · 224 lines · 23 tokens per session scan A e6676056480f

Subscribe to this mod's changes

.NET Upgrade is an agent published in the GitHub repository github/awesome-copilot (38,647 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 1,659 once invoked, about $0.0001 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-09-03.