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/azure/azure-sdk-for-java/azsdk-java-patch-mergebacknpx skills add Azure/azure-sdk-for-java --skill azsdk-java-patch-mergebackgit clone --depth 1 https://github.com/Azure/azure-sdk-for-javaWhat 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.00119 | $0.01364 |
| Opus 5 | $0.00060 | $0.00682 |
| Sonnet 5 | $0.00024 | $0.00273 |
| Haiku 4.5 | $0.00012 | $0.00136 |
Grade A, and why
azsdk-common-patch-mergeback 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 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.
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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Patch Release Merge-back
Prepare a PR that merges the version, CHANGELOG, and downstream pom.xml
updates produced by a patch release (on a release/patch/YYYYMMDD branch) back
into main. Patches revert CHANGELOG.md and version files to the last stable
release, so a naive merge creates many conflicts. This skill encodes how to
resolve each file type correctly.
Triggers
WHEN: "merge-back PR", "merge back patches", "patch release merge-back", "bring patch releases into main", "reconcile the patch branch" DO NOT USE FOR: triggering an SDK release, incrementing versions for a new patch cycle, code generation.
Inputs (variables)
Two values drive the whole workflow. Both come from the "Increment versions
for patch releases" PR (opened by azure-sdk-automation[bot]) that targets the
patch branch:
| Variable | How to determine it | Current value |
|---|---|---|
RELEASE_BRANCH |
The branch the "Increment versions" PR targets: release/patch/YYYYMMDD. |
release/patch/20260701 |
PATCH_DATE |
Derived from the branch name YYYYMMDD → YYYY-MM-DD. Used in CHANGELOG entries. |
2026-07-01 |
If either value is ambiguous, ask the user to confirm before proceeding.
Critical Rules (read first)
- Only the last two commits of
RELEASE_BRANCHcarry the updates to bring back. Diff againstRELEASE_BRANCH~2to scope the change set. - Never edit
pom.xmlby hand. It is regenerated byeng/versioning/update_versions.pyafterversion_client.txtis correct. - Do not touch
README.mdfiles. Run the version script with--skip-readmeso READMEs are left unchanged (README updates are handled separately). version_client.txt: update only thedependency-versionof SDK libraries that changed on the release branch; always keep thecurrent-versionfrommain. Never reset beta versions tobeta.1.CHANGELOG.md: keep thePATCH_DATEentry from the release branch; every other line must matchmain. Do not invent or edit any other CHANGELOG content.- Base the merge-back branch on
main, not on the release branch.
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.
- 2d ago First seen · 101 lines · 119 tokens per session scan A ee4737d1aacc
azsdk-common-patch-mergeback is a skill published in the GitHub repository Azure/azure-sdk-for-java (2,565 stars, last pushed today), licensed MIT. It adds 119 tokens to every session and 1,364 once invoked, about $0.0006 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
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…