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/cosmosgit 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/cosmos)<a href="https://agentmods.dev/instructions/azure/azure-sdk-for-rust/cosmos"><img src="https://agentmods.dev/badge/instructions/azure/azure-sdk-for-rust/cosmos.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.00121 | $0.00121 |
| Opus 5 | $0.00060 | $0.00060 |
| Sonnet 5 | $0.00024 | $0.00024 |
| Haiku 4.5 | $0.00012 | $0.00012 |
Grade A, and why
azure-sdk-for-rust cosmos.instructions.md 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 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.
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
Cosmos SDK Instructions
- CONSIDER all instructions in the sdk/cosmos/AGENTS.md file and the sdk/cosmos/.github/instructions folder when making changes to any files in the sdk/cosmos folder or its subfolders in addition to those in the AGENTS.md file and the .github/instructions folder.
- PREFER the Cosmos specific instructions in the sdk/cosmos/AGENTS.md file or the sdk/cosmos/.github/instructions folder over the general instructions in the .github/instructions folder if there are any conflicts.
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 · 9 lines · 121 tokens per session scan A 180e0aad8edd
azure-sdk-for-rust cosmos.instructions.md is an instructions file published in the GitHub repository Azure/azure-sdk-for-rust (885 stars, last pushed today), licensed MIT. It adds 121 tokens to every session, 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 instructions, from other repositories
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.
azure-sdk-for-go go-mod-standards.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 tsp-location.instructions.md
Instructions for Azure/azure-sdk-for-go, covering pre-requisites, regen and shortcuts.
azure-sdk-for-go go-tests.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.