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 ivegamsft/basecoat --skill dotnet-modernizationgit clone --depth 1 https://github.com/ivegamsft/basecoatWrote 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/ivegamsft/basecoat/dotnet-modernization)<a href="https://agentmods.dev/skills/ivegamsft/basecoat/dotnet-modernization"><img src="https://agentmods.dev/badge/skills/ivegamsft/basecoat/dotnet-modernization.svg" alt="Measured on agentmods" 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.00091 | $0.00329 |
| Opus 5 | $0.00046 | $0.00164 |
| Sonnet 5 | $0.00018 | $0.00066 |
| Haiku 4.5 | $0.00009 | $0.00033 |
Grade A, and why
dotnet-modernization 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 today.
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.
What it actually says
.NET Modernization
Use this skill when evaluating, planning, or executing migration from legacy .NET Framework or older .NET targets to modern .NET.
When to use
- Inventorying a solution before modernization
- Creating phased upgrade plans and risk controls
- Reviewing package/framework compatibility and breaking changes
- Defining test and release gates for modernization waves
Inputs
- Solution and project files (
*.sln,*.csproj) - Current runtime and framework versions
- NuGet package graph (direct and transitive)
- CI test coverage and deployment constraints
Outputs
- Modernization assessment summary
- Phased migration plan with checkpoints
- Dependency remediation recommendations
- Test and rollout strategy
References
- ./references/breaking-changes.md
What ships with it
2 files 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.
- today First seen · 46 lines · 91 tokens per session scan A 3d651e64bf11
dotnet-modernization is a skill published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed today), licensed MIT. It adds 91 tokens to every session and 329 once invoked, about $0.0005 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-08.
Other skills, from other repositories
maintain-discatsharp
Review, modify, test, document, or release the DisCatSharp repository. Use for DisCatSharp source changes, API additions and migrations, Discord payload models, serialization, command synchronization, Gateway dispatch, REST behavior, analyzer work, multi-target testing, DocFX generation, release notes, and repository…
compiler-commit
Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.
commit
Auto-fix, lint, test, and commit changes with a conventional commit message.
address-review
Read PR review comments from GitHub, evaluate, address, and reply.
vhs-e2e-gif
Record a test run, a TUI session, or any terminal command as a GIF with VHS and attach it to a GitHub PR as a release-hosted asset, never a repo commit. Use when asked to record an e2e run, demo a fix on a PR, attach a GIF or screen recording to a pull request, show a test passing visually, or produce a terminal…
code-review
Review .NET changes for bugs, regressions, architectural drift, missing tests, incorrect async or disposal behavior, and platform-specific pitfalls before you approve or merge them. USE FOR: reviewing a pull request or patch in a .NET repository; checking for behavioral regressions, API misuse, or missing tests…