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/instructions/pwsh.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/pwsh)<a href="https://agentmods.dev/instructions/azure/azure-sdk-for-rust/pwsh"><img src="https://agentmods.dev/badge/instructions/azure/azure-sdk-for-rust/pwsh.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.00864 | $0.00864 |
| Opus 5 | $0.00432 | $0.00432 |
| Sonnet 5 | $0.00173 | $0.00173 |
| Haiku 4.5 | $0.00086 | $0.00086 |
Grade A, and why
azure-sdk-for-rust pwsh.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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PowerShell Script Instructions
Path Handling
- Always use
[System.IO.Path]::Combineinstead ofJoin-Path- Use the full form:
([System.IO.Path]::Combine($path1, $path2, ...)) - Example:
([System.IO.Path]::Combine($PSScriptRoot, '..', 'common', 'scripts', 'common.ps1')) - This ensures consistent path handling across all platforms
- Use the full form:
Command Invocation
- Use
Invoke-LoggedCommandfor invoking external commands- Commands should be logged unless they output to stderr that needs to be processed
- Use
-GroupOutputto collapse output in CI logs - Use
-DoNotExitOnFailedExitCodewhen you need to handle exit codes manually - Example:
Invoke-LoggedCommand "cargo build --keep-going" -GroupOutput - Example with error handling:
Invoke-LoggedCommand "cargo test ..." -GroupOutput -DoNotExitOnFailedExitCode
Output Grouping
- Use
LogGroupStartandLogGroupEndto collapse verbose output- Use for output that is verbose or not relevant in most cases (e.g., large JSON dumps, detailed test output)
- Example:
LogGroupStart "Raw JSON Output" Get-Content $jsonFile | ForEach-Object { Write-Host $_ } LogGroupEnd
Console Output
- Do not use emojis in console output
- Use plain text instead
- Bad:
Write-Host "✅ Tests passed" - Good:
Write-Host "Tests passed"
Code Organization
- Extract common code patterns into functions
- If you see similar code blocks repeated, extract them into a reusable function
- Functions should have clear parameters and return values
- Example: Extract test execution logic into a shared function rather than duplicating it
- Do not modify
eng/commonscripts directly- Treat
eng/common/as shared upstream engineering infrastructure - Add repository-specific helpers under
eng/scripts/shared/instead of changingeng/common/directly
- Treat
- Use
eng/scripts/shared/common.ps1for repository-specific shared helpers- Add new helper imports there and have scripts import that file rather than dot-sourcing multiple repo-local helper files individually
- Put new functions in new or existing helper files under
eng/scripts/shared/as appropriate
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.
- 7d ago First seen · 91 lines · 864 tokens per session scan A 47a33e9451b4
azure-sdk-for-rust pwsh.instructions.md is an instructions file published in the GitHub repository Azure/azure-sdk-for-rust (884 stars, last pushed today), licensed MIT. It adds 864 tokens to every session, about $0.0043 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
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).
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.
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.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.