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-dev/documentationgit clone --depth 1 https://github.com/Azure/azure-devWhat 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.00608 | $0.00608 |
| Opus 5 | $0.00304 | $0.00304 |
| Sonnet 5 | $0.00122 | $0.00122 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
azure-dev documentation.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.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Maintenance
This repository uses a structured documentation system under docs/ at the repo root.
When making changes to the codebase, keep the documentation current.
Documentation Structure
docs/
├── README.md — Documentation index and navigation
├── concepts/ — Core mental models, terminology, feature lifecycle
├── guides/ — Task-oriented how-tos for contributors
├── reference/ — Schemas, flags, environment variables, feature status
└── architecture/ — System overviews, design context, ADRs
When to Update Documentation
- New command or flag: Update
docs/guides/adding-a-new-command.mdif the pattern changes; updatedocs/reference/feature-status.mdwith the new feature's stage. - User-visible behavior change: Update relevant command docs/help when behavior affects workflows, especially
--no-promptor CI/script semantics. - New environment variable: Add it to
cli/azd/docs/environment-variables.md(canonical), and keepdocs/reference/environment-variables.mdin sync when appropriate. - New extension capability: Update
docs/architecture/extension-framework.mdanddocs/guides/creating-an-extension.md. - Feature stage change: Update
docs/reference/feature-status.mdwhen a feature graduates (alpha → beta → stable). - New concept or term: Add it to
docs/concepts/glossary.md. - Architecture decision: Create a new ADR using the template at
docs/architecture/adr-template.md. - New hosting target or language: Update
docs/reference/feature-status.mdanddocs/concepts/glossary.md. - Product rebrand or compatibility name: Use the current product name in user-facing prose, while preserving legacy/internal identifiers only where required by code, telemetry, APIs, or compatibility.
Documentation Placement Guide
| Content type | Location |
|---|---|
| Term or concept definition | docs/concepts/glossary.md |
| Contributor how-to | docs/guides/ |
| Configuration reference | docs/reference/ |
| System design or ADR | docs/architecture/ |
| Implementation design details | cli/azd/docs/design/ |
| Extension development details | cli/azd/docs/extensions/ |
| Code style standards | cli/azd/docs/style-guidelines/ |
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 · 48 lines · 608 tokens per session scan A 15979e2b37b4
azure-dev documentation.instructions.md is an instructions file published in the GitHub repository Azure/azure-dev (567 stars, last pushed 2d ago), licensed MIT. It adds 608 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
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.
skills copilot-instructions.md
Copilot instructions for microsoft/skills, covering copilot instructions for agent skills, project overview, ⚠️ fresh information first, core principles and 1. think before coding.
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-rust pwsh.instructions.md
Instructions for Azure/azure-sdk-for-rust, covering powershell script instructions, path handling, command invocation, output grouping and console output.