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 skills add alexpizarro/azure-lean-stack-skills --skill orchestrating-azure-deploymentsgit clone --depth 1 https://github.com/alexpizarro/azure-lean-stack-skillsWrote 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/skills/alexpizarro/azure-lean-stack-skills/orchestrating-azure-deployments)<a href="https://agentmods.dev/skills/alexpizarro/azure-lean-stack-skills/orchestrating-azure-deployments"><img src="https://agentmods.dev/badge/skills/alexpizarro/azure-lean-stack-skills/orchestrating-azure-deployments/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/skills/alexpizarro/azure-lean-stack-skills/orchestrating-azure-deployments"><img src="https://agentmods.dev/badge/skills/alexpizarro/azure-lean-stack-skills/orchestrating-azure-deployments.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.00096 | $0.02070 |
| Opus 5 | $0.00048 | $0.01035 |
| Sonnet 5 | $0.00019 | $0.00414 |
| Haiku 4.5 | $0.00010 | $0.00207 |
Grade A, and why
orchestrating-azure-deployments 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 11d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrating Azure Deployments (Azure Lean Stack)
Thin router for Azure app deployments. Holds no domain knowledge of its own — every task is delegated to a single-purpose sub-skill or to Microsoft's azure-skills plugin.
Stack defaults: React 19 + TypeScript | Azure Functions v4 (Node 22) | Azure SQL Serverless | Bicep IaC | GitHub Actions OIDC | branch-per-environment
Last verified: May 2026
The deployment model — branch-per-environment
Before delegating anything else, internalise the deployment model. One branch in the repo = one isolated Azure resource group. main is never connected to Azure — it's for local dev only. test → test RG. production → prod RG. New branch + one OIDC credential = new isolated environment.
This model is non-negotiable. Every sub-skill assumes it. See references/architecture-decisions.md decision #0 for the full rationale (and the OIDC subject lockdown that makes it safe).
How to use this skill
Identify the user's task, then delegate. Never inline domain knowledge from a sub-skill — read the sub-skill's SKILL.md and follow it.
Routing table
| User intent | Skill to invoke |
|---|---|
| "Scaffold a new Azure web app" / "set up a new project" | scaffolding-azure-bicep-infrastructure |
| "Set up OIDC" / "configure GitHub Actions for Azure" / "create service principals" | configuring-azure-oidc-for-github-actions |
| "Add a SQL migration" / "set up the migration system" | managing-azure-sql-migrations |
| "Deploy a React + Functions app" / "SWA" / "Static Web Apps" | deploying-azure-static-web-apps |
| "Add a timer trigger" / "queue trigger" / "AI workload" / "FC1" / "Flex Consumption" | deploying-fc1-flex-consumption-functions |
| "Docker on Azure" / "Container Apps" / "WebSocket/SSE" / "long-running server" / "background job" | deploying-azure-container-apps |
| "Blob storage cost" / "lifecycle rules" / "tier to cool/cold" / "delete old blobs" | optimizing-azure-blob-storage-cost |
| "Transactional email" / "ACS email" / "send email from Azure" | adding-azure-communication-services-email |
| "Add observability" / "App Insights" / "metric alerts" / "5xx alerts" | instrumenting-azure-app-insights |
| "Multi-tenant" / "one RG per customer" / "per-tenant isolation" | scaffolding-multi-tenant-azure-apps |
| "Recurring trigger" / "schedule" / "Logic App" / "Power-Automate-like flow" / "ping every N minutes" | scheduling-with-azure-logic-apps-consumption |
| "Run locally" / "offline" / "docker" / "local SQL" / "Azurite" / "seed local data" / "set up dev environment" | developing-azure-apps-locally |
| "Reduce cost" / "audit SKUs" / "stay on free tier" / "consumption-only" | applying-azure-cost-guardrails |
| "Deploy failed" / "diagnose this error" / "AADSTS70021" / "BCP258" / "LocationNotAvailable" | diagnosing-azure-deployment-failures |
| "I learned something" / "promote a learning to gotchas" / "capture this lesson" | curating-azure-deployment-learnings |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 113 lines · 96 tokens per session scan A 827d89beae97
orchestrating-azure-deployments is a skill published in the GitHub repository alexpizarro/azure-lean-stack-skills (1 stars, last pushed 1mo ago), licensed MIT. It adds 96 tokens to every session and 2,070 once invoked, about $0.0005 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-31.
Other skills, from other repositories
azure-expert
Expert-level Microsoft Azure cloud platform, services, and architecture. Use when the user mentions cloud, Microsoft platforms, Azure Functions, or Cosmos DB.
iac-common
UTILITY SKILL — Shared IaC deploy patterns for Bicep + Terraform agents: deployment strategies, circuit breaker, known deploy issues. WHEN: "phased deployment", "circuit breaker", "deploy strategy", "deploy issue", "shared IaC pattern". DO NOT USE FOR: preflight (azure-validate), code generation (azure-bicep-patterns…
aws-iac-change-safety-review
Review AWS infrastructure-as-code changes across CDK, CloudFormation, SAM, Terraform, Serverless Framework, generated templates, plans, stack updates, change sets, and drift. Use when the user asks whether an AWS IaC deployment is safe, what a change set will do, why a resource replacement will happen, or how to…
Tag Hygiene Enforcer
Establishes and enforces a tag / label taxonomy across all clouds. Runs coverage audits, policy-as-code guardrails, and remediation campaigns until coverage is above 95%.
infra-plan
Plan infrastructure changes — Terraform modules, Helm charts, CI/CD pipelines. Use when the user wants to add or modify cloud infrastructure, Kubernetes resources, or deployment pipelines.
terraform-iac
Terraform and OpenTofu infrastructure as code best practices - generate HCL configurations, module patterns, state management, CI/CD workflows, and cloud provider templates for AWS, GCP, Azure.