Azure SDK for .NET is a repository containing the actively developed C# libraries that applications use to work with Azure services. It is for .NET developers building software that connects to Azure storage, management, and other cloud services.
Borrowing it
Nothing to install: this file belongs to Azure/azure-sdk-for-net. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Azure/azure-sdk-for-net/main/.github/skills/azure-sdk-mgmt-pr-review/SKILL.mdgit clone --depth 1 https://github.com/Azure/azure-sdk-for-netWrote 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/azure/azure-sdk-for-net/azure-sdk-mgmt-pr-review)<a href="https://agentmods.dev/skills/azure/azure-sdk-for-net/azure-sdk-mgmt-pr-review"><img src="https://agentmods.dev/badge/skills/azure/azure-sdk-for-net/azure-sdk-mgmt-pr-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/skills/azure/azure-sdk-for-net/azure-sdk-mgmt-pr-review"><img src="https://agentmods.dev/badge/skills/azure/azure-sdk-for-net/azure-sdk-mgmt-pr-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00026 | $0.03627 |
| Opus 5 | $0.00013 | $0.01813 |
| Sonnet 5 | $0.00005 | $0.00725 |
| Haiku 4.5 | $0.00003 | $0.00363 |
Grade A, and why
azure-sdk-mgmt-pr-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 8d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Azure .NET Mgmt SDK PR Review
Review Azure SDK for .NET management library PRs in three phases: 1. Versioning, 2. API Review, 3. Breaking Change Detection. Run phases in order. Versioning failures are blocking, but continue into API review unless the baseline cannot be determined reliably.
Phase 1: Versioning Review
Check the package .csproj, CHANGELOG.md, and compatibility files. Comment on every violation. Phase 1 violations are blocking; use the Finding Severity policy to determine the final review event across all phases.
Rules:
- No major version bump unless .NET architects explicitly require a coordinated management-SDK major bump. Flag
1.x->2.0.0as Critical. - Do not remove
ApiCompatVersion. It enforces compatibility against the last stable release. If removed, recover the prior value from base branch or latest released tag for later phases. - No new ApiCompat baseline entries. Do not suppress compatibility errors; mitigate with customization code or generator/spec fixes. Exception:
WirePathAttributeremoval diffs may use targeted entries ineng/apicompatbaselines/<Project>.xmlwhen they are the only remaining ApiCompat differences.
Continue to Phase 2 unless the versioning issue makes the API-review scope impossible to determine, e.g. ApiCompatVersion was removed and no prior stable baseline can be recovered. In that narrow case, request changes and say API review was skipped because the baseline is unknown.
Phase 2: API Review
Review only new or changed public API relative to the latest stable release. Existing shipped API that is unchanged is out of scope.
Scope
- Read
ApiCompatVersionfrom.csproj. If absent and never present, treat the whole API surface as new and skip breaking-change checks. - If present, fetch the released API file from tag
<PackageName>_<Version>, e.g.Azure.ResourceManager.Foo_1.0.0, undersdk/<service>/<PackageName>/api/<PackageName>.net10.0.csor older TFM variants. - Use CI ApiCompat results as the authoritative automated signal for binary compatibility and parameter names/order. Repository history and current
mainare context, not evidence that an API shipped. - Diff released API against the PR API file. Review only added/modified types, members, and enums.
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.
- 8d ago Changed 493c1f482ed1
- 12d ago First seen · 190 lines · 26 tokens per session scan A 1590d9be0fd3
azure-sdk-mgmt-pr-review is a skill published in the GitHub repository Azure/azure-sdk-for-net (6,049 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 3,627 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
cosmos-pre-commit-validation
Run pre-commit checks for a specific set of crates. Use this when validating changes under sdk/cosmos before committing or during code review.
cosmos-design-struct
Enforce consistent struct design conventions across sdk/cosmos crates. Validates visibility modifiers, field privacy, #[nonexhaustive] usage, and construction API patterns (Default/new with with setters, or optional separate builders with builder()/build()), and construction correctness on public structs. Can auto-fix…
update-pr
Update the pull request for the current session. Use when the user wants to push new changes to an existing PR.
clean-abap
Clean ABAP coding standards and best practices. Use when writing ABAP code, reviewing ABAP code, or refactoring ABAP code to ensure it follows SAP's official Clean ABAP style guide. Covers naming conventions, modern language constructs, class/method design, error handling, formatting, comments, and unit testing…
code-analysis
Use the free built-in .NET SDK analyzers and analysis levels with gradual Roslyn warning promotion. USE FOR: the repo wants first-party .NET analyzers; CI should fail on analyzer warnings; the team needs AnalysisLevel or AnalysisMode guidance. DO NOT USE FOR: third-party analyzer selection by itself; formatting-only…
sonarjs
Use SonarJS-derived rules in .NET repositories that ship JavaScript or TypeScript frontends and need deeper bug-risk, code-smell, or cognitive-complexity checks than a minimal ESLint baseline. USE FOR: SonarQube, SonarCloud, or eslint-plugin-sonarjs setups; frontend code smells; cognitive complexity and deeper…