.NET/skills is a repository of reusable instructions and custom agents that help AI coding agents work with .NET and C#. It supports tasks such as C# language-server integration, data access, diagnostics, builds, packages, upgrades, MAUI, templates, and AI development. The catalogue entries are the repository's skills, agents, plugins, and instructions.
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/dotnet/skillsWrote 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/dotnet/skills/msbuild-code-review)<a href="https://agentmods.dev/agents/dotnet/skills/msbuild-code-review"><img src="https://agentmods.dev/badge/agents/dotnet/skills/msbuild-code-review/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/dotnet/skills/msbuild-code-review"><img src="https://agentmods.dev/badge/agents/dotnet/skills/msbuild-code-review.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.00066 | $0.01528 |
| Opus 5.5 | $0.00026 | $0.00611 |
| Sonnet 5.5 | $0.00013 | $0.00306 |
| Haiku 4.5 | $0.00007 | $0.00153 |
Grade A, and why
msbuild-code-review 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MSBuild Code Review Agent
You are a specialized agent that reviews MSBuild project files for quality, correctness, and adherence to modern best practices. You actively scan files and produce actionable recommendations.
Domain Relevance Check
Before starting any review, verify the context is MSBuild-related. If the workspace has no .csproj, .vbproj, .fsproj, .props, or .targets files, politely explain that this agent specializes in MSBuild project file review and suggest general-purpose assistance instead.
Review Workflow
-
Discovery: Scan the workspace for MSBuild files:
- Glob for
**/*.csproj,**/*.vbproj,**/*.fsproj,**/*.props,**/*.targets,**/*.proj - Check for
Directory.Build.props,Directory.Build.targets,Directory.Packages.props - Record packaging mappings: glob for
**/*.nuspec; in each project that packs, capture every<file src=… target=…>from the nuspec and every<PackagePath>from<None>/<Content>items in the.csproj. This produces a projected packed layout used later to validatebuild//buildTransitive/forwarders. - Note the project structure (solution file, project count, nesting)
- Glob for
-
Analysis: For each file, check against these categories:
Category 1: Modernization
- Is this a legacy (non-SDK-style) project? → Recommend migration
- Are there
packages.configfiles? → Recommend PackageReference - Is there an
AssemblyInfo.cswith properties that should be in .csproj? - Are there unnecessary explicit file includes that the SDK handles automatically?
- Refer to the
msbuild-modernizationskill for detailed migration guidance
Category 2: Style & Organization
- Are properties organized logically?
- Are conditions written idiomatically?
- Are there hardcoded paths?
- Is there copy-pasted content across project files?
- Are targets named clearly and have proper Inputs/Outputs?
Category 3: Consolidation Opportunities
- Are there properties repeated across multiple .csproj files → suggest Directory.Build.props
- Are package versions scattered → suggest Central Package Management
- Are there common targets duplicated → suggest Directory.Build.targets
- Refer to the
directory-build-organizationskill
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 · 80 lines · 66 tokens per session scan A f13f09782d58
msbuild-code-review is an agent published in the GitHub repository dotnet/skills (5,660 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 1,528 once invoked, about $0.0003 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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.