Azure SDK for Java is a collection of Java libraries that let applications connect to and manage Azure services. Java developers use its client libraries to consume services and its management libraries to configure Azure resources. The catalogue add-ons support development with these libraries.
Borrowing it
Nothing to install: this file belongs to Azure/azure-sdk-for-java. 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-java/main/.github/skills/azsdk-common-sdk-release/SKILL.mdgit clone --depth 1 https://github.com/Azure/azure-sdk-for-javaWrote 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-java/azsdk-common-sdk-release)<a href="https://agentmods.dev/skills/azure/azure-sdk-for-java/azsdk-common-sdk-release"><img src="https://agentmods.dev/badge/skills/azure/azure-sdk-for-java/azsdk-common-sdk-release.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.00085 | $0.00591 |
| Opus 5 | $0.00043 | $0.00296 |
| Sonnet 5 | $0.00017 | $0.00118 |
| Haiku 4.5 | $0.00009 | $0.00059 |
Grade A, and why
azsdk-common-sdk-release 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.
This is a copy
100% identical to azsdk-common-sdk-release — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDK Release
This skill checks release readiness and triggers the Azure SDK release pipeline for packages that are already prepared, guiding the user through prerequisite validation, readiness review, and the final pipeline launch with required approval steps.
Triggers
USE FOR: release SDK, trigger release, check release readiness, release pipeline, publish package, ship SDK WHEN: "release SDK", "trigger release", "check release readiness", "release pipeline", "publish package", "ship SDK" DO NOT USE FOR: SDK development, code generation, pipeline debugging, release plan creation
Rules
- Requires the
azure-sdk-mcpserver; there is no CLI fallback for the release workflow. - Collect
packageNameandlanguage, then run the readiness check before attempting to trigger release. - If release is triggered, show the pipeline link and remind the user that the release stage still requires approval.
MCP Tools
| Tool | Purpose |
|---|---|
azure-sdk-mcp:azsdk_release_sdk |
Check release readiness and/or trigger the release pipeline |
Steps
- Collect Info — Get
packageNameandlanguagefrom the user. Optionally getbranch(defaults to main). - Determine Intent — If the user explicitly asks to "check readiness" or "check if ready", run
azure-sdk-mcp:azsdk_release_sdkwithcheckReady: true. Otherwise, proceed to trigger the release directly. - Trigger Release — Run
azure-sdk-mcp:azsdk_release_sdkwithcheckReady: false(the default). Show pipeline link and inform user they must approve the release stage. - Review Results — If the release fails due to readiness issues, display failing checks and guide user to resolve.
Examples
- "Check if azure-storage-blob is ready for release"
- "Trigger release for @azure/core-rest-pipeline on JavaScript"
Troubleshooting
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 First seen · 49 lines · 85 tokens per session scan A d368ffe5db9b
azsdk-common-sdk-release is a skill published in the GitHub repository Azure/azure-sdk-for-java (2,565 stars, last pushed today), licensed MIT. It adds 85 tokens to every session and 591 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to azsdk-common-sdk-release, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
update-changelog
Update the CHANGELOG.md files of C# projects. Parameters: csroot C# SDK repository root.
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.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
azure-communication-chat-java
Build real-time chat applications with Azure Communication Services Chat Java SDK. Use when implementing chat threads, messaging, participants, read receipts, typing notifications, or real-time chat features.
azure-communication-common-java
Azure Communication Services common utilities for Java. Use when working with CommunicationTokenCredential, user identifiers, token refresh, or shared authentication across ACS services.
azure-data-tables-java
Build table storage applications with Azure Tables SDK for Java. Use when working with Azure Table Storage or Cosmos DB Table API for NoSQL key-value data, schemaless storage, or structured data at scale.