dotnet-upgrade-agent.USAGE

An agent that plans and, with approval, upgrades a .NET solution to a newer version. It can address framework changes, outdated APIs, package updates, and verification.

In plain words
What is it for?
Use it to plan or perform target-framework upgrades, identify obsolete APIs, update packages, and verify each stage with builds and tests.
Why use it?
It helps manage the breaking changes and checks that can make a .NET upgrade risky across multiple projects.

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/stefanthecode/dotnet-ai-toolkit/dotnet-upgrade-agent.usage
Clone the repo
git clone --depth 1 https://github.com/StefanTheCode/dotnet-ai-toolkit
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 226 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.00000 $0.00226
Opus 5 $0.00000 $0.00113
Sonnet 5 $0.00000 $0.00045
Haiku 4.5 $0.00000 $0.00023

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

Security

Grade A, and why

dotnet-upgrade-agent.USAGE 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.

agents/dotnet-upgrade-agent.USAGE.md · 15 lines

What it actually says

How to use — .NET Upgrade Agent

What it is. An agent that plans and (with approval) executes a .NET version upgrade across a solution — TFM bumps, breaking-change remediation, obsolete-API replacement, package updates, and per-stage verification.

When to reach for it. Upgrading to a newer .NET (e.g. 6→8→9→10) or migrating target frameworks.

How to use it. Point it at your solution (path or GitHub URL). Example prompts:

  • "Upgrade this solution from .NET 6 to .NET 9."
  • "Plan a migration to .NET 10 and flag the breaking changes."
  • "What obsolete APIs will break when I upgrade?"

Get the best out of it. Let it upgrade one major at a time and verify (build + tests) between steps. Review its plan before it edits — it asks first. It defers deep rewrites to legacy-modernization-assistant.

Won't do. It won't power through a red build or skip verification to finish faster.

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 · 15 lines · 0 tokens per session scan A c567efcaae2c

Subscribe to this mod's changes

dotnet-upgrade-agent.USAGE is an agent published in the GitHub repository StefanTheCode/dotnet-ai-toolkit (19 stars, last pushed 23d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 226 tokens. 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-30.