Azure SDK for Rust is a collection of Rust libraries, organized as separate crates, for interacting with Azure services. Rust developers use the crates and examples to build applications that work with Azure. The catalogue entries provide coding-agent skills, instructions, agents, and MCP integrations for working with the SDK.
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-rust/create-hotfixnpx skills add Azure/azure-sdk-for-rust --skill create-hotfixgit clone --depth 1 https://github.com/Azure/azure-sdk-for-rustWrote 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-rust/create-hotfix)<a href="https://agentmods.dev/skills/azure/azure-sdk-for-rust/create-hotfix"><img src="https://agentmods.dev/badge/skills/azure/azure-sdk-for-rust/create-hotfix.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.00020 | $0.00532 |
| Opus 5 | $0.00010 | $0.00266 |
| Sonnet 5 | $0.00004 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
create-hotfix 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.
What it actually says
Create a Hotfix
Use the bundled script for deterministic discovery and git operations. Run all commands from the repository root.
-
List workspace crates:
python3 .github/skills/create-hotfix/create_hotfix.py list-cratesUse a single-select prompt to ask the user which crate to patch, using the crate names from the JSON output.
-
Prepare the hotfix:
python3 .github/skills/create-hotfix/create_hotfix.py prepare <crate-name>The command fetches tags and
maindirectly fromhttps://github.com/Azure/azure-sdk-for-rust, finds the latest stable<crate-name>@<version>tag, calculates the next patch version, createshotfix/<crate-name>-<version>from that tag unless already on ahotfix/branch, and returns candidate commits frommainas JSON. -
If candidates were returned, prompt the user with a multiselect containing each candidate's SHA and deterministic summary. Allow selecting none.
-
If commits are selected, preserve their displayed order and run:
python3 .github/skills/create-hotfix/create_hotfix.py cherry-pick <sha>...The script automatically resolves
Cargo.lockconflicts by taking--ours, then regenerating it with:cargo generate-lockfile --manifest-path Cargo.tomlIf the JSON result has a
waitingstatus, prompt the user to resolve and stage the listed conflicts. Remain waiting for the user to confirm they are ready, then run:python3 .github/skills/create-hotfix/create_hotfix.py continueRepeat this step if another commit conflicts. Do not abort or skip commits. Only show the final message after the script returns a
completestatus. -
Report the selected crate, base tag, patch version, branch, and cherry-picked commits. Tell the user:
Make any additional hotfix changes on this branch. Do not merge this branch into
main; cherry-pick any new fixes intomainseparately. See the Azure SDK hotfix branch policy for more information.
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 · 60 lines · 20 tokens per session scan A 7f0208ab0c2e
create-hotfix is a skill published in the GitHub repository Azure/azure-sdk-for-rust (885 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 532 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-09-03.
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)…
mitigate-breaking-changes
Patterns and techniques for mitigating breaking changes in Azure management-plane SDKs. Covers SDK-side customizations (partial classes, CodeGenType, CodeGenSuppress) and TypeSpec decorator customizations (clientName, access, markAsPageable, alternateType, hierarchyBuilding).
translate-a-sample
Translate the Azure SDK sample from python to C# and generate markdownn file for the sample. Parameters: C# SDK repository root; python SDK repository root; Package name: one of Azure.AI.Projects, Azure.AI.Projects.Agents or Azure.AI.Extensions.OpenAI; The name of sample file in Python SDK repository.
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.
setup-rust-pre-commit
Set up fast pre-commit hooks for a Rust repo — format and lint the staged changes only, with CI left as the real gate.