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 agentmods add skills/dotnet/maui/code-reviewnpx skills add dotnet/maui --skill code-reviewgit clone --depth 1 https://github.com/dotnet/mauiWhat 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 | $0.00110 | $0.07455 |
| Opus 5 | $0.00055 | $0.03728 |
| Sonnet 5 | $0.00022 | $0.01491 |
| Haiku 4.5 | $0.00011 | $0.00745 |
Grade A, and why
code-review scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL -H 'Accept: application/vnd.github.patch' \ How it starts
The opening of the file, as written. The whole thing — 448 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Skill
Standalone skill that evaluates PR code changes for correctness, safety, performance, and consistency with .NET MAUI conventions. Can be invoked directly by users or by other agents/skills.
Trigger phrases: "review code for PR #XXXXX", "code review PR #XXXXX", "review this PR's code", "analyze code changes in PR", "check PR code quality"
Do NOT use for: "what does PR #XXXXX do?", "summarize PR", "describe the changes", or any informational query — just answer those directly without invoking this skill.
How this differs from other skills:
pr-review— End-to-end PR workflow (4 phases: pre-flight, gate, try-fix, report). Use when you want the full pipeline including test verification and fix attempts.pr-finalize— Verifies PR title/description match implementation + light code review. Use before merging.code-review(this skill) — Deep code-only review with MAUI domain rules. Use when you want a thorough code analysis without running tests or modifying the PR.
Core Principles
- Independence-first — Form your assessment from the code BEFORE reading the PR description. This prevents anchoring on the author's framing
- Full-context — Read entire source files, not just diffs. Check callers, consumers, and git history
- Empirical grounding — Reference specific code, line numbers, and call sites. No vague concerns
- Severity calibration — Distinguish errors from warnings from suggestions. Not everything is critical
- Failure-mode probing — Challenge your own conclusions with real failure scenarios, not softballs
- Propagation-aware guards — For an early return, idempotency flag, or latch above downstream side effects, trace every set/clear path and a repeat call after recipients or state change. If that trace exposes concrete misbehavior, do not dismiss it as rare or rationalize it into
LGTM: useNEEDS_DISCUSSIONwhile the failure remains unresolved, orNEEDS_CHANGESwhen the exact state transition verifies a ❌ Error. - Authentication is not availability — A public GitHub PR remains reviewable when
ghis unauthenticated. Never stop or ask for a token merely because aghcommand failed; pivot immediately to anonymous public REST/web retrieval.
What ships with it
20 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.
- tests/eval.inline-findings.vally.yaml 9.7 KB
- tests/eval.producer-trace.vally.yaml 4.7 KB
- tests/eval.trim-aot.vally.yaml 16 KB
- tests/eval.vally.yaml 25 KB
- tests/fixtures/producer-trace/change.diff 2.9 KB
- tests/fixtures/producer-trace/src/.github/skills/review-test-failures/scripts/Gather-TestFailureContext.ps1 2.4 KB runs code
- tests/fixtures/producer-trace/src/eng/devices/run-windows-devicetests.cmd 867 B runs code
- tests/fixtures/trim-aot/.gitattributes 106 B
- tests/fixtures/trim-aot/case-a/change.diff 1.2 KB
- tests/fixtures/trim-aot/case-a/src/Controls/src/Core/Hosting/AppHostBuilderExtensions.cs 1.1 KB
- tests/fixtures/trim-aot/case-b/change.diff 1.3 KB
- tests/fixtures/trim-aot/case-b/src/Controls/src/Core/Hosting/AppHostBuilderExtensions.cs 1.2 KB
- tests/fixtures/trim-aot/case-c/change.diff 1.4 KB
- tests/fixtures/trim-aot/case-c/src/Controls/src/Core/Hosting/AppHostBuilderExtensions.cs 1.0 KB
- tests/fixtures/trim-aot/shared/src/Controls/src/Build.Tasks/nuget/buildTransitive/netstandard2.0/Microsoft.Maui.Controls.targets 685 B
- tests/fixtures/trim-aot/shared/src/Core/src/Handlers/HybridWebView/HybridWebViewHandler.cs 365 B
- tests/fixtures/trim-aot/shared/src/Core/src/Hosting/MauiHandlersCollectionExtensions.cs 575 B
- tests/fixtures/trim-aot/shared/src/Core/src/RuntimeFeature.cs 695 B
- tests/hermeticity.vally.yaml 6.5 KB
- tests/soak.capability.vally.yaml 23 KB
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.
- 2d ago First seen · 448 lines · 110 tokens per session scan A 8255b2761e53
code-review is a skill published in the GitHub repository dotnet/maui (23,317 stars, last pushed 2d ago), licensed MIT. It adds 110 tokens to every session and 7,455 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
dpg-migration
Migration logic for Azure SDK for .NET data-plane libraries migrating from AutoRest/Swagger to TypeSpec-based generation. Uses MCP tools from the generator-agent server for automated deterministic fixes.
csharp-azure-spector-coverage-gaps
Discovers and implements gaps in Spector test coverage for the Azure C# HTTP client emitter. Use when asked to find missing Spector scenarios, add Spector test coverage, or implement a specific Spector spec for the Azure C# emitter. Can also compare coverage between the Azure dashboard and the Standard (TypeSpec core)…
auto-build-repair
Headless, bounded repair of custom-code build failures in an already-generated Azure SDK PR. Thin wrapper over the shared azure-sdk-mcp:azsdkcustomizedcodeupdate engine in custom-code-only scope (editScope: CustomCode); the skill owns the iterate-until-green loop, capped by a per-language maxIterations read from…
azure-sdk-mgmt-pr-review
Review Azure SDK management-plane pull requests, check naming conventions, API compatibility, and code quality.
mgmt-review-comment-resolution
Resolve review comments on Azure management-plane .NET SDK PRs. Handles renaming types/properties, changing property types, and other API surface adjustments by updating TypeSpec client.tsp and regenerating.
mitigate-breaking-changes
Patterns and techniques for mitigating breaking changes during Azure management-plane SDK migration from Swagger/AutoRest to TypeSpec. Covers SDK-side customizations (partial classes, CodeGenType, CodeGenSuppress) and TypeSpec decorator customizations (clientName, access, markAsPageable, alternateType…