azure-dev: Instructions file for GitHub Copilot

.github/instructions/extensions.instructions.md

azure-dev extensions.instructions.md is an instructions file for GitHub Copilot from Azure/azure-dev. It costs 697 tokens per session, scanned A, original, MIT.

Coding instructions for extensions to Azure Developer CLI, a command-line tool for building, deploying, and monitoring applications on Azure.

In plain words
What is it for?
Use them when adding or reviewing Azure Developer CLI extensions, especially subscription login, delete operations, cleanup, and style-guide compliance.
Why use it?
They prevent authentication mistakes in multi-tenant accounts and require careful handling of destructive commands and saved local state.

Instructions file for GitHub Copilot ✓ vendor

Written for GitHub Copilot: a Copilot instructions file. Also seen: mentions AGENTS.md.

This is Azure/azure-dev's own configuration. It tells GitHub Copilot how to work on azure-dev itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything azure-dev configures →

About the project

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.

Azure/azure-dev · 570 stars · on GitHub · aka.ms

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/Azure/azure-dev/main/.github/instructions/extensions.instructions.md
Clone the repo
git clone --depth 1 https://github.com/Azure/azure-dev

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for azure-dev extensions.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/azure/azure-dev/extensions/github.svg)](https://agentmods.dev/instructions/azure/azure-dev/extensions)
Your own site
<a href="https://agentmods.dev/instructions/azure/azure-dev/extensions"><img src="https://agentmods.dev/badge/instructions/azure/azure-dev/extensions/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.

agentmods 80×15 button for azure-dev extensions.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/azure/azure-dev/extensions"><img src="https://agentmods.dev/badge/instructions/azure/azure-dev/extensions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 697 This file is loaded in full into every session.
When invoked 697 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00697 $0.00697
Opus 5.5 $0.00279 $0.00279
Sonnet 5.5 $0.00139 $0.00139
Haiku 4.5 $0.00070 $0.00070

Measured 9d ago against content hash f6d5a7b70b40, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

azure-dev extensions.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 9d 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.

.github/instructions/extensions.instructions.md · 50 lines

What it actually says

applyTo:

  • cli/azd/extensions/**

  • When accessing a Subscription from PromptSubscription(), always use Subscription.UserTenantId (user access tenant) for credential creation, NOT Subscription.TenantId (resource tenant). For multi-tenant/guest users these differ, and using TenantId causes authentication failures. The LookupTenant() API already returns the correct user access tenant.

  • When adding or reviewing destructive extension commands, verify the service API contract and local cleanup behavior end-to-end: confirm whether the API supports the requested delete scope, handle empty successful delete responses, avoid redundant pre-checks that later operations already cover, and clean up any persisted local state such as conversation or session IDs. Use the resource identity persisted by deployment, including custom/adopted names, and respect ownership when deciding what to delete.

  • Follow extension guidelines in: cli/azd/docs/extensions/extensions-style-guide.md. If the work violates any of these principles, include a link to the guide so the user can read it and get ahead of some of the problems.

  • Reject explicitly supplied flags that cannot take effect. Use cmd.Flags().Changed("<flag>") so explicit empty values are validated rather than treated as omitted. Explicit selectors take precedence over persisted values and defaults. Name conflicting inputs in the error and use exterrors.Validation(exterrors.CodeConflictingArguments, message, suggestion) where available, otherwise follow the extension's validation-error pattern.

  • Redact credentials from URLs before printing to terminal, logs, or error messages. URLs may carry credentials in the userinfo component (user:pass@host) or in the query string (SAS tokens, sig= parameters). Clear URL.User and drop RawQuery and Fragment before passing a URL to any output function, error message, or log call. redactURL in cli/azd/pkg/azdext/pagination.go and redactURLForDebug in cli/azd/extensions/azure.ai.training/pkg/client show the shape, but both only strip the query and fragment, so clear the userinfo as well. This applies to download URLs, clone URLs, registry addresses, and any URL stored in artifacts or uploaded CI outputs. Add a non-disclosure test that feeds a credential-bearing URL and asserts no sensitive portion appears in the output.

  • Keep output on the injected writer when a command handler or helper receives one; do not bypass it with direct writes to os.Stdout or os.Stderr, including in debug and diagnostic paths. Extensions that do not expose a writer must follow their local AGENTS.md output conventions. See "Keep terminal output on the injected writer" in cli/azd/AGENTS.md.

  • When behavior narrows, narrow the help text and doc comments with it.

  • Validate locally checkable inputs and conflicts before authentication or mutations. Invalid inputs must leave project files and persisted environment values unchanged.

  • Keep schema, decoding, request mapping, and runtime validation consistent for inline and $ref definitions. Reject unsupported fields instead of silently dropping authored configuration.

Changes

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.

  1. 9d ago Changed · +5 lines · +4 tokens per session f6d5a7b70b40
  2. 1mo ago First seen · 45 lines · 693 tokens per session scan A 43728a113e2f

Subscribe to this mod's changes

azure-dev extensions.instructions.md is an instructions file published in the GitHub repository Azure/azure-dev (570 stars, last pushed today), licensed MIT. It adds 697 tokens to every session, about $0.0028 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.

Related

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,581 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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.

deepseek-ai/deepseek-harness · 4,261 tokens

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).

microsoft/vscode · 2,731 tokens