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/azsdk-common-prepare-release-plan/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/azsdk-common-prepare-release-plan)<a href="https://agentmods.dev/skills/azure/azure-sdk-for-net/azsdk-common-prepare-release-plan"><img src="https://agentmods.dev/badge/skills/azure/azure-sdk-for-net/azsdk-common-prepare-release-plan/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/azsdk-common-prepare-release-plan"><img src="https://agentmods.dev/badge/skills/azure/azure-sdk-for-net/azsdk-common-prepare-release-plan.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.00231 | $0.02599 |
| Opus 5 | $0.00115 | $0.01300 |
| Sonnet 5 | $0.00046 | $0.00520 |
| Haiku 4.5 | $0.00023 | $0.00260 |
Grade A, and why
azsdk-common-prepare-release-plan 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 12d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- azsdk-common-prepare-release-plan — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare Release Plan
This skill creates, gets, updates, abandons, and links SDK PRs to release plan work items for Azure SDK releases, helping gather required release data, validate spec inputs, and link related approvals or SDK pull requests without exposing internal work item URLs.
Triggers
USE FOR: create release plan, get release plan, update release plan, update API spec in release plan, update SDK details in release plan, abandon release plan, link SDK PR to plan, namespace approval, check release plan status WHEN: "create release plan", "get release plan", "update release plan", "abandon release plan", "link SDK PR to plan", "namespace approval", "check release plan status" DO NOT USE FOR: SDK code generation, pipeline troubleshooting, API review feedback
Rules
- Do not display Azure DevOps work item URLs; only provide the Release Plan Link and ID.
- Require an API spec PR link or a TypeSpec project path before creating or updating a plan.
- Validate that the spec PR repository matches the requested API release type before creation.
- Release plan tools accept either a Release Plan ID or an Azure DevOps work item ID — pass whichever the user provides. Each tool resolves the value automatically (trying it as a Release Plan ID first, then as a work item ID), so you do not need to call
azure-sdk-mcp:azsdk_get_release_planfirst just to translate one ID into the other.
MCP Tools
| Tool | Purpose |
|---|---|
azure-sdk-mcp:azsdk_create_release_plan |
Create a new release plan |
azure-sdk-mcp:azsdk_get_release_plan |
Get release plan details by ID |
azure-sdk-mcp:azsdk_get_release_plan_for_spec_pr |
Find release plan by spec PR URL |
azure-sdk-mcp:azsdk_update_release_plan |
Update release plan metadata |
azure-sdk-mcp:azsdk_update_api_spec_pull_request_in_release_plan |
Update API spec PR URL in plan |
azure-sdk-mcp:azsdk_update_sdk_details_in_release_plan |
Update SDK/package details in plan |
azure-sdk-mcp:azsdk_abandon_release_plan |
Abandon a release plan |
azure-sdk-mcp:azsdk_link_sdk_pull_request_to_release_plan |
Link SDK PR to release plan |
azure-sdk-mcp:azsdk_link_namespace_approval_issue |
Link namespace approval issue |
What ships with it
4 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.
- 12d ago First seen · 180 lines · 231 tokens per session scan A a0f6fcdb1d1b
azsdk-common-prepare-release-plan is a skill published in the GitHub repository Azure/azure-sdk-for-net (6,050 stars, last pushed yesterday), licensed MIT. It adds 231 tokens to every session and 2,599 once invoked, about $0.0012 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.
create-draft-pr
Create a draft pull request for the current session. Use when the user wants to open a draft PR with the session's changes.
create-pr
Create a pull request for the current session. Use when the user wants to open a PR with the session's changes.
release-notes
Update CHANGELOG.md and README.md for an Azure SDK for Java package based on a GitHub PR. Use when the user wants to write or update release notes, changelogs, or readme docs from a PR reference.
codegen
Generate code from TypeSpec via tsp-client (update, sync, generate). Requires a tsp-location.yaml in the current working directory. Supports updating the commit hash before running.
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…