Azure Developer CLI (azd) is a command-line tool for building, deploying, and operating applications on Azure. Developers use it to move through application workflows such as coding, building, deployment, and monitoring with Azure templates and resources. Its catalogue entries help AI agents work with azd and Azure application projects.
Borrowing it
Nothing to install: this file belongs to Azure/azure-dev. 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-dev/main/.github/instructions/documentation.instructions.mdgit clone --depth 1 https://github.com/Azure/azure-devWrote 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-dev/documentation)<a href="https://agentmods.dev/instructions/azure/azure-dev/documentation"><img src="https://agentmods.dev/badge/instructions/azure/azure-dev/documentation/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-dev/documentation"><img src="https://agentmods.dev/badge/instructions/azure/azure-dev/documentation.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.00608 | $0.00608 |
| Opus 5.5 | $0.00243 | $0.00243 |
| Sonnet 5.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 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.
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.
- 1mo ago 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 (570 stars, last pushed today), licensed MIT. It adds 608 tokens to every session, about $0.0024 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).