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/sdk/cosmos/.github/instructions/cosmos.changelog.instructions.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/cosmos.changelog)<a href="https://agentmods.dev/instructions/azure/azure-sdk-for-rust/cosmos.changelog"><img src="https://agentmods.dev/badge/instructions/azure/azure-sdk-for-rust/cosmos.changelog/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/instructions/azure/azure-sdk-for-rust/cosmos.changelog"><img src="https://agentmods.dev/badge/instructions/azure/azure-sdk-for-rust/cosmos.changelog.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.00605 | $0.00605 |
| Opus 5 | $0.00302 | $0.00302 |
| Sonnet 5 | $0.00121 | $0.00121 |
| Haiku 4.5 | $0.00060 | $0.00060 |
Grade A, and why
azure-sdk-for-rust cosmos.changelog.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 9d 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
-
Follow the Azure SDK changelog instructions for Rust as the primary reference for changelogs unless they conflict with Cosmos-specific requirements outlined below or in other
cosmos.*.instructions.mdfiles. -
Goal: every customer-visible change gets a changelog entry so users can quickly understand the risk/benefit of upgrading.
-
Never modify already released sections (anything not marked "Unreleased"). Only add entries under the current "(Unreleased)" version.
-
If the PR title starts with
[Internal], do not change anyCHANGELOG.mdfiles. -
Add entries under an existing category header (for example: "Features Added", "Breaking Changes", "Bugs Fixed", "Other Changes"). A single PR may produce multiple entries when it spans multiple categories or distinct customer-visible changes.
- Do not create new category headers.
- Put each entry under the most appropriate existing category.
-
Entry format:
- Prefer the existing style used in the file.
- When the file uses PR-linked bullets, use the same pattern:
- Prefer placing the PR link at the end, matching existing Cosmos changelog entries:
- <one-line summary of the change>. ([#12345](https://github.com/Azure/azure-sdk-for-rust/pull/12345))
- Prefer placing the PR link at the end, matching existing Cosmos changelog entries:
- If you are working on a local branch and there is no PR yet, you may add the one-line summary without the link.
- Once a PR exists (even before merge), update the entry to include the PR link.
-
PR number/link discovery (do this automatically when a PR exists):
- Determine the current branch name:
git rev-parse --abbrev-ref HEAD. - Prefer using GitHub CLI if available/authenticated:
gh pr view --repo Azure/azure-sdk-for-rust --json number,url- or
gh pr list --repo Azure/azure-sdk-for-rust --head <forkOwner>:<branch> --json number,url --limit 1
- If
ghis unavailable, search GitHub PRs by head branch (works in a browser):- Query:
is:pr head:<forkOwner>:<branch> - URL:
https://github.com/Azure/azure-sdk-for-rust/pulls?q=is%3Apr+head%3A<forkOwner>%3A<branch>
- Query:
- Determine the current branch name:
-
For the first unreleased version section, keep all standard category headers present even if some are empty.
-
Keep entries concise, accurate, and relevant to the release.
-
Reference example (style only):
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.
- 9d ago First seen · 39 lines · 605 tokens per session scan A 3e0d2cf037fc
azure-sdk-for-rust cosmos.changelog.instructions.md is an instructions file published in the GitHub repository Azure/azure-sdk-for-rust (884 stars, last pushed 2d ago), licensed MIT. It adds 605 tokens to every session, about $0.0030 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.