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 instructions/azure/azure-sdk-for-rust/agents-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/instructions/azure/azure-sdk-for-rust/agents-md)<a href="https://agentmods.dev/instructions/azure/azure-sdk-for-rust/agents-md"><img src="https://agentmods.dev/badge/instructions/azure/azure-sdk-for-rust/agents-md.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 | $0.03628 | $0.03628 |
| Opus 5 | $0.01814 | $0.01814 |
| Sonnet 5 | $0.00726 | $0.00726 |
| Haiku 4.5 | $0.00363 | $0.00363 |
Grade B, and why
azure-sdk-for-rust AGENTS.md scanned grade B with 1 finding 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 5d 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
2. **Static Analysis**: Must pass `cargo clippy` without warnings How it starts
The opening of the file, as written. The whole thing — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This document provides guidance for AI agents (e.g., GitHub Copilot, MCP servers, or LLM-based assistants) interacting with the Azure SDK for Rust repository.
Repository Overview
The Azure SDK for Rust provides Rust language bindings and client libraries for Azure services, following the Azure SDK Design Guidelines for Rust.
- Primary Language: Rust
- Minimum Supported Rust Version (MSRV): found in the root
Cargo.tomlfile - Key Technologies: Cargo, TypeSpec, OpenTelemetry, Test Proxy
Repository Structure
.
├── sdk/ # Service-specific crates organized by service
│ └── {service}/ # Service directory (e.g., "keyvault", "storage")
│ ├── {crate}/ # Service crate (e.g., "azure_security_keyvault_secrets")
│ ├── assets.json # Pointer to test recordings (may be under {crate}/)
│ ├── test-resources.bicep # Test resource definitions (may be under {crate}/)
│ └── tsp-location.yaml # Pointer to TypeSpec in azure-rest-api-specs (may be under {crate}/)
├── eng/ # Engineering system scripts and common tooling
├── doc/ # Additional documentation
├── .github/
│ ├── instructions/ # Agent instruction files for specific tasks
│ └── skills/ # Copilot skills (e.g., check-spelling, lint-markdown)
├── CONTRIBUTING.md # Contribution guidelines (see for detailed workflows)
└── README.md # Repository overview
Agent Capabilities
Always check if there is an MCP tool or skill available before performing operations manually, including listing Azure subscriptions, deploying resources, setting up a new crate, generating code, and other common workflows.
All new crates must be generated from TypeSpec specifications in [Azure/azure-rest-api-specs]. TypeSpec specifications are located under specification/{service}/. Use the create-crate skill to set up a new crate.
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.
- 5d ago First seen · 306 lines · 3,628 tokens per session scan B e00c8999020e
azure-sdk-for-rust AGENTS.md is an instructions file published in the GitHub repository Azure/azure-sdk-for-rust (885 stars, last pushed yesterday), licensed MIT. It adds 3,628 tokens to every session, about $0.0181 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
azure-sdk-for-net AGENTS.md
AGENTS.md instructions for Azure/azure-sdk-for-net, covering azure sdk for .net - ai agent guidelines, repository overview, purpose and scope, repository structure and agent interaction guidelines.
azure-sdk-for-net copilot-instructions.md
Copilot instructions for Azure/azure-sdk-for-net, covering project overview, prerequisites, folder structure, azure generator and azure management generator.
azure-sdk-for-go AGENTS.md
AGENTS.md instructions for Azure/azure-sdk-for-go, covering agents.md, repository overview, key documentation, go version support and agent capabilities and boundaries.
azure-sdk-for-go go-examples.instructions.md
Instructions for Azure/azure-sdk-for-go, a project described as: This repository is for active development of the Azure SDK for Go. For consumers of the SDK we recommend visiting our public developer docs at.
azure-sdk-for-go copilot-instructions.md
Copilot instructions for Azure/azure-sdk-for-go, covering generated code — do not suggest changes, prerequisites, local sdk generation and package lifecycle (typespec), authoritative reference and default behaviors.
azure-sdk-for-go go-code.instructions.md
Instructions for Azure/azure-sdk-for-go: All code should follow the guidelines from the Azure Go SDK Guidelines. This document is a summary of the most important guidelines to follow when contributing to the Azure Go SDK.