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/extensionsgit 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.00693 | $0.00693 |
| Opus 5 | $0.00347 | $0.00347 |
| Sonnet 5 | $0.00139 | $0.00139 |
| Haiku 4.5 | $0.00069 | $0.00069 |
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 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
applyTo:
- cli/azd/extensions/**
-
When accessing a
SubscriptionfromPromptSubscription(), always useSubscription.UserTenantId(user access tenant) for credential creation, NOTSubscription.TenantId(resource tenant). For multi-tenant/guest users these differ, and usingTenantIdcauses authentication failures. TheLookupTenant()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.
-
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-set flags that cannot take effect; never silently drop them. When a flag is explicitly supplied (check via
cmd.Flags().Changed("<flag>")) but the selected code path ignores it — for example,--inspector-portwith--no-client, or any agent-creation flag during a reuse flow, or init-only flags during a standalone-eject run — return a clear error that names the conflicting inputs. Automation scripts that pass explicit flags and receive a success exit code must be able to trust that those flags were honored. In extensions that provideinternal/exterrors, report flag conflicts withexterrors.Validation(exterrors.CodeConflictingArguments, message, suggestion). Otherwise, follow the extension's established 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). ClearURL.Userand dropRawQueryandFragmentbefore passing a URL to any output function, error message, or log call.redactURLincli/azd/pkg/azdext/pagination.goandredactURLForDebugincli/azd/extensions/azure.ai.training/pkg/clientshow 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.Stdoutoros.Stderr, including in debug and diagnostic paths. Extensions that do not expose a writer must follow their localAGENTS.mdoutput conventions. See "Keep terminal output on the injected writer" incli/azd/AGENTS.md. -
When behavior narrows, narrow the help text and doc comments with it.
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 · 45 lines · 693 tokens per session scan A 43728a113e2f
azure-dev extensions.instructions.md is an instructions file published in the GitHub repository Azure/azure-dev (567 stars, last pushed yesterday), licensed MIT. It adds 693 tokens to every session, about $0.0035 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.