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/github-pullrequest.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/github-pullrequest)<a href="https://agentmods.dev/instructions/azure/azure-sdk-for-rust/github-pullrequest"><img src="https://agentmods.dev/badge/instructions/azure/azure-sdk-for-rust/github-pullrequest/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/github-pullrequest"><img src="https://agentmods.dev/badge/instructions/azure/azure-sdk-for-rust/github-pullrequest.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.00287 | $0.00287 |
| Opus 5.5 | $0.00115 | $0.00115 |
| Sonnet 5.5 | $0.00057 | $0.00057 |
| Haiku 4.5 | $0.00029 | $0.00029 |
Grade A, and why
azure-sdk-for-rust github-pullrequest.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 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
Instructions for GitHub Pull Requests
-
GitHub Pull Requests should follow the standard form for Git commits:
title of no more than 50 characters multi-line descriptions -
Summarize changes for a title of no more than 50 characters ideally, with a hard stop at 80 characters.
-
Descriptions can be multiple lines or even paragraphs using markdown.
-
Descriptions may contain markdown.
-
Descriptions should not repeat a lot of content already found in the changed files.
-
Summarize changes for each file if no more than 10 files are changed.
-
If multiple files contain the same changes, group them together when summarizing changes.
-
Try to reason why changes were made and not about what was changed.
-
If any added comments in changed files reference fixing an issue like "Fixes #1234" include that same text in the description.
-
If multiple issues are fixed or resolved, include that same text separately for each issue like "Fixes #1234 and fixes #5678".
-
Do not leave coding agent plans in the description: always summarize changes before the PR is ready to review.
Code Requirements
-
All source files must have a copyright header using a language-appropriate comment e.g.,
// Copyright (c) Microsoft Corporation. All rights reserved. // Licensed under the MIT License.
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 · 30 lines · 287 tokens per session scan A bf60e999f817
azure-sdk-for-rust github-pullrequest.instructions.md is an instructions file published in the GitHub repository Azure/azure-sdk-for-rust (886 stars, last pushed today), licensed MIT. It adds 287 tokens to every session, about $0.0011 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-08-30.
Other instructions, from other repositories
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).