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.
npx skills add StefanTheCode/dotnet-ai-toolkit --skill legacy-package-migratorgit 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/skills/stefanthecode/dotnet-ai-toolkit/legacy-package-migrator)<a href="https://agentmods.dev/skills/stefanthecode/dotnet-ai-toolkit/legacy-package-migrator"><img src="https://agentmods.dev/badge/skills/stefanthecode/dotnet-ai-toolkit/legacy-package-migrator/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/skills/stefanthecode/dotnet-ai-toolkit/legacy-package-migrator"><img src="https://agentmods.dev/badge/skills/stefanthecode/dotnet-ai-toolkit/legacy-package-migrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 79 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00139 | $0.02420 |
| Opus 5.5 | $0.00056 | $0.00968 |
| Sonnet 5.5 | $0.00028 | $0.00484 |
| Haiku 4.5 | $0.00014 | $0.00242 |
Grade A, and why
legacy-package-migrator 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 2mo 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Legacy Package Migrator (packages.config -> PackageReference -> CPM)
Move a .NET Framework solution off packages.config and onto PackageReference, then lift all versions into a single Directory.Packages.props using Central Package Management (CPM). The goal is one source of truth for every NuGet version across every project -- including third-party extension projects -- so nobody ends up with two versions of the same package in one solution.
Input — point it at your code
You don't need pasted files. Work from whatever target the user gives:
- A solution / repo root — the
.slnand every project under it - A folder — scan for
packages.config,*.csproj,app.config/web.config - A single project — one
.csproj+ itspackages.config - A GitHub URL — clone first:
git clone --depth 1 <url> /tmp/repo && cd /tmp/repo
Discover the packaging state yourself with Glob/Grep/Bash instead of asking for a paste:
grep -rl "packages.config" <target> | grep -vi "/obj/\|/bin/"
# version drift across the solution:
grep -rhn "id=\"Newtonsoft.Json\"" --include=packages.config <target>
grep -rn "<PackageReference" --include=*.csproj <target>
Tell the user which projects you scanned, and always show the drift inventory before writing Directory.Packages.props.
When this runs
The user has a packages.config-based solution (usually .NET Framework, often many projects) and wants to modernize package management, pin transitive versions, or stop version drift across modules and vendor extensions. They may point at a folder, paste a .csproj / packages.config, or just describe the mess.
If you don't have the files, ask for: the solution's project list, one representative .csproj + its packages.config, and whether third-party/vendor projects live in the same solution or reference the same packages.
Why this order matters
Do it in two stages, never one. Each stage is independently verifiable and revertible:
- Stage 1 --
packages.config->PackageReference(per project). Behavior-preserving; versions still live in each.csproj. - Stage 2 --
PackageReference-> Central Package Management. Hoist every version into oneDirectory.Packages.props; strip versions from projects.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 162 lines · 139 tokens per session scan A f08f9039393a
legacy-package-migrator is a skill published in the GitHub repository StefanTheCode/dotnet-ai-toolkit (26 stars, last pushed 2mo ago), licensed MIT. It adds 139 tokens to every session and 2,420 once invoked, about $0.0006 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.
legacy-package-migrator compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| legacy-package-migratorStefanTheCode/dotnet-ai-toolkit | Skill | 26 | 2mo ago | MIT | A | 139 | Claude Code |
| build-and-testmicrosoft/agent-framework | Skill | 15k | yesterday | MIT | A | 26 | Claude Code, Codex |
| agui-dotnet-streaming-chatag-ui-protocol/ag-ui | Skill | 17k | yesterday | MIT | A | 223 | Claude Code |
| azure-mgmt-apicenter-dotnetmicrosoft/skills | Skill | 3.2k | yesterday | MIT | A | 97 | Claude Code |
| migrate-xunit-to-xunit-v3dotnet/skills | Skill | 5.8k | yesterday | MIT | A | 149 | Claude Code |
| migrate-dotnet8-to-dotnet9dotnet/skills | Skill | 5.8k | yesterday | MIT | A | 176 | Claude Code |
| template-instantiationdotnet/skills | Skill | 5.8k | yesterday | MIT | A | 168 | Claude Code |