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-pipeline-fixer/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-pipeline-fixer)<a href="https://agentmods.dev/skills/azure/azure-sdk-for-java/azsdk-common-pipeline-fixer"><img src="https://agentmods.dev/badge/skills/azure/azure-sdk-for-java/azsdk-common-pipeline-fixer/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-java/azsdk-common-pipeline-fixer"><img src="https://agentmods.dev/badge/skills/azure/azure-sdk-for-java/azsdk-common-pipeline-fixer.svg" alt="Reviewed on agentmods" width="80" 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.00150 | $0.00767 |
| Opus 5 | $0.00075 | $0.00383 |
| Sonnet 5 | $0.00030 | $0.00153 |
| Haiku 4.5 | $0.00015 | $0.00077 |
Grade A, and why
azsdk-common-pipeline-fixer 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 10d 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-pipeline-fixer — 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipeline Fixer
This skill automatically fixes Azure SDK CI/CD pipeline failures. It analyzes the failure, identifies the root cause, applies code changes, and verifies the fix locally using build, check, and test tools before committing.
Rules
- Requires the
azure-sdk-mcpserver and a local clone of the SDK language repo. - Work on the PR branch — the failing code is there, not main.
- Analyze first, then apply the minimal code change for the root cause.
- Verify ONLY via the azsdk MCP package tools (build → check → tests); never raw shell build/test commands.
- Never fix infrastructure failures (timeouts, crashes, throttling) — recommend retry. Iterate up to 3 times, then report.
MCP Tools
| Tool | Purpose |
|---|---|
azure-sdk-mcp:azsdk_verify_setup |
Verify local environment is ready |
azure-sdk-mcp:azsdk_package_build_code |
Build the package locally |
azure-sdk-mcp:azsdk_package_run_check |
Run validation/lint/typecheck locally |
azure-sdk-mcp:azsdk_package_run_tests |
Run tests locally |
Prerequisites: azure-sdk-mcp server required. Local clone of the affected SDK language repo. Language build tools installed.
Steps
- Find analysis - Reuse an existing analysis from the PR comments; if none, view the
azsdk-common-pipeline-analysisskill. - Classify - Fixable (test, type, lint, import, assertion errors) vs retry (infrastructure) vs escalate (breaking API, credentials).
- Locate - Identify the affected package, its path, and the files/lines to change.
- Fix - Read the failing code at the cited lines and apply the minimal fix.
- Verify - Run
azsdk_package_build_code→azsdk_package_run_check→azsdk_package_run_testson the package; all must pass. If the environment isn't ready, runazsdk_verify_setup. Never substitute raw shell build/test commands. - Iterate & commit - On failure, revise and re-verify (max 3 attempts). Once all pass, commit with a descriptive message.
What ships with it
1 file 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.
- 10d ago First seen · 52 lines · 150 tokens per session scan A 62cfffcd4aa0
azsdk-common-pipeline-fixer is a skill published in the GitHub repository Azure/azure-sdk-for-java (2,565 stars, last pushed today), licensed MIT. It adds 150 tokens to every session and 767 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to azsdk-common-pipeline-fixer, differing in 0 lines, and is treated as a copy.
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.
056-design-avoid-breaking-changes
Use when you need to review a plan, OpenSpec change, specification, or implementation proposal for breaking-change risk across commands, skills, generated outputs, XML sources, README/docs, tests, CI, APIs, schemas, configuration, data, migration, and release guidance. This should trigger for requests such as Review…
compiler-commit
Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.
author-test
Generate a test given sample. Parameters: C# SDK repository root; Package name: one of Azure.AI.Projects, Azure.AI.Projects.Agents or Azure.AI.Extensions.OpenAI; the sample to use as a starting point for the test.
update-changelog
Update the CHANGELOG.md files of C# projects. Parameters: csroot C# SDK repository root.
commit
Auto-fix, lint, test, and commit changes with a conventional commit message.