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/github-pullrequestgit clone --depth 1 https://github.com/Azure/azure-sdk-for-rustWhat 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.00287 | $0.00287 |
| Opus 5 | $0.00143 | $0.00143 |
| Sonnet 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 yesterday.
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.
- yesterday 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 (885 stars, last pushed 3d ago), licensed MIT. It adds 287 tokens to every session, about $0.0014 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-net 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
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
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
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.