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 skills/azure/azure-dev/azdnpx skills add Azure/azure-dev --skill azdgit 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.00052 | $0.00825 |
| Opus 5 | $0.00026 | $0.00413 |
| Sonnet 5 | $0.00010 | $0.00165 |
| Haiku 4.5 | $0.00005 | $0.00082 |
Grade A, and why
azd 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 2d 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.
What it actually says
azd is a tool for getting your application to the cloud, in minutes. Use azd, rather than az, when:
- You want a simple, repeatable way to get your application in Azure for ad-hoc development
- You want a simple way to get your application to Azure using Azure DevOps or GitHub Actions.
- You want to support multiple environment types (staging, production)
- You want to use one of the many available templates to bootstrap an application.
This is a small sample of the templates available:
- JavaScript/TypeScript web/API starter (Container Apps; React + Node.js API):
- azd init --template Azure-Samples/todo-nodejs-mongo-aca
- JavaScript/TypeScript web app starters (App Service):
- azd init --template Azure-Samples/app-service-javascript-sap-cap-quickstart (Node.js/SAP CAP; its azure.yaml lives under azd-sub/, so run
cd azd-subbeforeazd up) - azd init --template Azure-Samples/app-service-javascript-sap-cloud-sdk-quickstart (TypeScript/SAP Cloud SDK)
- azd init --template Azure-Samples/app-service-javascript-sap-cap-quickstart (Node.js/SAP CAP; its azure.yaml lives under azd-sub/, so run
- JavaScript/TypeScript serverless starter (Functions):
- azd init --template Azure-Samples/azd-functions-sharepoint-webhooks (TypeScript/JavaScript Azure Functions)
- Python web/API starter (App Service):
- azd init --template Azure-Samples/todo-python-mongo (FastAPI + MongoDB)
- azd init --template Azure-Samples/azd-simple-fastapi-appservice (minimal FastAPI starter)
- Python web/API starter (Container Apps):
- azd init --template Azure-Samples/todo-python-mongo-aca (FastAPI + MongoDB)
Canonical flows:
- First-time deploy:
azd auth login->azd init->azd up - Separate infra/app steps:
azd provision->azd deploy - New environment:
azd env new <name>->azd up - Select environment:
azd env select <name> - Redeploy app only:
azd deploy - Tear down resources:
azd down - Remove an environment completely:
azd down->azd env remove <name>
az to azd mental model:
- Use this as a translation guide, not an exact command mapping.
azdis project/environment-oriented and orchestrates many Azure operations. - Login/subscription context:
az login/az account set->azd auth login(+ environment-aware workflows viaazd envcommands)
- Resource creation + deployment:
- Multi-step
az group create+az deployment * create+ app deployment commands ->azd up
- Multi-step
- Infra-only updates:
az deployment * create(infra focus) ->azd provision
- App-only updates:
- Service-specific deploy commands (for example webapp/container/function deploy flows) ->
azd deploy
- Service-specific deploy commands (for example webapp/container/function deploy flows) ->
- Environment/config handling:
- Manual variable/parameter handling in scripts ->
azd env new,azd env select, and.env-driven project settings
- Manual variable/parameter handling in scripts ->
- Resource teardown:
az group delete(or equivalent manual cleanup) ->azd down- After resource teardown, remove local environment state with
azd env remove <name>
Template discovery:
- Templates: Use https://azure.github.io/awesome-azd/ for full community gallery.
- GitHub: https://github.com/Azure/azure-dev/
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.
- 2d ago First seen · 57 lines · 52 tokens per session scan A fdf1921ef671
azd is a skill published in the GitHub repository Azure/azure-dev (567 stars, last pushed 2d ago), licensed MIT. It adds 52 tokens to every session and 825 once invoked, about $0.0003 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 skills, from other repositories
dpg-migration
Migration logic for Azure SDK for .NET data-plane libraries migrating from AutoRest/Swagger to TypeSpec-based generation. Uses MCP tools from the generator-agent server for automated deterministic fixes.
csharp-azure-spector-coverage-gaps
Discovers and implements gaps in Spector test coverage for the Azure C# HTTP client emitter. Use when asked to find missing Spector scenarios, add Spector test coverage, or implement a specific Spector spec for the Azure C# emitter. Can also compare coverage between the Azure dashboard and the Standard (TypeSpec core)…
auto-build-repair
Headless, bounded repair of custom-code build failures in an already-generated Azure SDK PR. Thin wrapper over the shared azure-sdk-mcp:azsdkcustomizedcodeupdate engine in custom-code-only scope (editScope: CustomCode); the skill owns the iterate-until-green loop, capped by a per-language maxIterations read from…
azure-sdk-mgmt-pr-review
Review Azure SDK management-plane pull requests, check naming conventions, API compatibility, and code quality.
mgmt-review-comment-resolution
Resolve review comments on Azure management-plane .NET SDK PRs. Handles renaming types/properties, changing property types, and other API surface adjustments by updating TypeSpec client.tsp and regenerating.
mitigate-breaking-changes
Patterns and techniques for mitigating breaking changes during Azure management-plane SDK migration from Swagger/AutoRest to TypeSpec. Covers SDK-side customizations (partial classes, CodeGenType, CodeGenSuppress) and TypeSpec decorator customizations (clientName, access, markAsPageable, alternateType…