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.
Borrowing it
Nothing to install: this file belongs to Azure/azure-sdk-for-rust. 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-rust/main/.github/skills/analyze-code/SKILL.mdgit 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/analyze-code)<a href="https://agentmods.dev/skills/azure/azure-sdk-for-rust/analyze-code"><img src="https://agentmods.dev/badge/skills/azure/azure-sdk-for-rust/analyze-code/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-rust/analyze-code"><img src="https://agentmods.dev/badge/skills/azure/azure-sdk-for-rust/analyze-code.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.00025 | $0.00272 |
| Opus 5.5 | $0.00010 | $0.00109 |
| Sonnet 5.5 | $0.00005 | $0.00054 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
analyze-code 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 1mo 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
Analyze changed packages
Run this as a final check after completing any prompt that changes repository files.
-
Collect changed files from Git, including staged, unstaged, untracked, and deleted files:
{ git diff --staged --name-only; git diff --name-only; git ls-files --others --exclude-standard -- 'sdk'; } | sort -u -
Assume service crates live under
sdk/<service-directory>/<crate-name>. For each changed file undersdk/, derive the candidate crate directory from the first three path segments and keep it only when<crate-directory>/Cargo.tomlexists. Include any crate names specified in the prompt, then collect and deduplicate all<crate-name>values as package names. -
Run the analyzer once from the repository root with all changed package names:
./eng/scripts/Analyze-Code.ps1 -PackageNames @('<crate-name-1>', '<crate-name-2>')
If neither changed files nor the prompt identify a service crate, report that no packages need analysis. Otherwise, report the packages analyzed and any failures.
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.
- 1mo ago First seen · 29 lines · 25 tokens per session scan A 678dc81f8c40
analyze-code is a skill published in the GitHub repository Azure/azure-sdk-for-rust (886 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 272 once invoked, about $0.0001 per session on Opus 5.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-17.
Other skills, from other repositories
generate-code-cs
Generate the code from typespec for C#. Parameter: C# SDK repository root location .
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.
rust-trait-object-layout
Rust trait object layout — DST fat pointers, vtable placement, generic last-field coercion surprise.
Debug Helper
Systematic logic error isolation.
Lint Hunter
Debugging compiler errors and tracing lifetimes.