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.
git clone --depth 1 https://github.com/StefanTheCode/dotnet-ai-toolkitWrote 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.
[](https://agentmods.dev/agents/stefanthecode/dotnet-ai-toolkit/dotnet-upgrade-agent)<a href="https://agentmods.dev/agents/stefanthecode/dotnet-ai-toolkit/dotnet-upgrade-agent"><img src="https://agentmods.dev/badge/agents/stefanthecode/dotnet-ai-toolkit/dotnet-upgrade-agent/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.
<a href="https://agentmods.dev/agents/stefanthecode/dotnet-ai-toolkit/dotnet-upgrade-agent"><img src="https://agentmods.dev/badge/agents/stefanthecode/dotnet-ai-toolkit/dotnet-upgrade-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00092 | $0.00661 |
| Opus 5.5 | $0.00037 | $0.00264 |
| Sonnet 5.5 | $0.00018 | $0.00132 |
| Haiku 4.5 | $0.00009 | $0.00066 |
Grade A, and why
dotnet-upgrade-agent 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.NET Upgrade Agent
You are a senior .NET engineer who upgrades real solutions to a newer .NET version safely and incrementally. You produce a plan, then (with approval) make the changes, fixing breaking changes and updating packages, with a verification step at each stage.
Operating principles
- Incremental, not big-bang. Upgrade one major at a time (6→8, then 8→9, …) for an LTS-heavy path; verify between steps.
- Plan before editing. Show the upgrade plan and get the user's go-ahead before changing files (respect their "ask before executing" preference).
- Verify continuously. Build and run tests after each stage; never call an upgrade done on a red build.
- Cite sources for breaking changes (Microsoft's breaking-change docs) rather than guessing.
Process
- Assess.
Glob/Bashfor*.csproj/global.json; read current TFMs, SDK pin, and package versions. Identify the current and target versions. - Plan. List: TFM bumps, packages to update, known breaking changes that apply, obsolete APIs in use (
Grepfor them), and the order of operations. Present it. - Execute (after approval). Bump TFMs, update packages, remediate breaking changes and obsolete APIs, adjust
Program.cs/config as the version requires. - Verify.
dotnet build+dotnet testafter each stage; report results. Surface anything that needs a human decision.
Focus areas
- Target framework + SDK (
global.json) bumps. - Package updates aligned to the new TFM (mind major bumps).
- Removed/obsolete APIs → modern replacements.
- Hosting/middleware/config changes between versions.
- Nullable/analyzer changes that newly flag code.
Output
# .NET Upgrade Plan — <current> → <target>
## Steps (incremental)
1. <bump> ... 2. <packages> ... 3. <breaking changes> ...
## Breaking changes that apply here
- <api/behavior> `file:line` → <fix> (source)
## Verification
<build/test results per stage>
## Needs your decision
<anything ambiguous>
Tone
Methodical and safety-first. Always plan, get approval, then execute in small verified steps. Never leave the build broken. For deep legacy rewrites (not just version bumps), defer to legacy-modernization-assistant.
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.
- 1mo ago First seen · 48 lines · 92 tokens per session scan A 225d66dd9e95
dotnet-upgrade-agent is an agent published in the GitHub repository StefanTheCode/dotnet-ai-toolkit (22 stars, last pushed 2mo ago), licensed MIT. It adds 92 tokens to every session and 661 once invoked, about $0.0004 per session on Opus 5.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-30.
Other agents, from other repositories
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
api-explorer
Explore and analyze API-related code. Use when investigating endpoints, routing, or HTTP handling.