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/archubbuck/workspace-architectWrote 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/archubbuck/workspace-architect/dotnet-upgrade)<a href="https://agentmods.dev/agents/archubbuck/workspace-architect/dotnet-upgrade"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/dotnet-upgrade/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/archubbuck/workspace-architect/dotnet-upgrade"><img src="https://agentmods.dev/badge/agents/archubbuck/workspace-architect/dotnet-upgrade.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.00023 | $0.01659 |
| Opus 5.5 | $0.00009 | $0.00664 |
| Sonnet 5.5 | $0.00005 | $0.00332 |
| Haiku 4.5 | $0.00002 | $0.00166 |
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 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.
This is a copy
100% identical to .NET 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.
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
- Run a discovery pass to enumerate all
*.slnand*.csprojfiles in the repository. - Detect the current .NET version(s) used across projects.
- Identify the latest available stable .NET version (LTS preferred) — usually
+2years ahead of the existing version. - Generate an upgrade plan to move from current → next stable version (e.g.,
net6.0 → net8.0, ornet7.0 → net9.0). - Upgrade one project at a time, validate builds, update tests, and modify CI/CD accordingly.
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 · 224 lines · 23 tokens per session scan A e6676056480f
.NET Upgrade is an agent published in the GitHub repository archubbuck/workspace-architect (19 stars, last pushed yesterday), licensed ISC. It adds 23 tokens to every session and 1,659 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to .NET Upgrade, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
code-reviewer
Senior Android code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, performance. Use for thorough code review before merge.
agentmaster-review
Cost-tiered adversarial code review. Use after implementers complete a plan, or on any diff, branch, or recent changes. Assumes the code is bad — poorly implemented, doesn't scale, violates YAGNI, SOLID, or DRY, hard to test, badly structured, insecure — and makes it prove otherwise with evidence gathered by scout and…
code-analyst
Mid-cost interpretation — trace how code works across files, reproduce and analyze test failures, research dependency changelogs and upgrade impact, run code-graph and architecture queries. Use when the answer requires reading between files, interpreting command output, or external research. Also the escalation target…
Library Curator
Curates changed skills, agents, instructions, workflows, and prompts in this lab by running frontmatter, link, and self-containment checks plus a README index sync, then proposes one fix list before editing anything.
react-reviewer
Expert React/JSX code reviewer specializing in hook correctness, render performance, server/client component boundaries, accessibility, and React-specific security. Use for any change touching .tsx/.jsx files or React component logic. MUST BE USED for React projects.
critic
../../src/claude/agents/critic.md.