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/danwahlin/github-azure-agentic-journeys/container-apps-deploymentnpx skills add DanWahlin/github-azure-agentic-journeys --skill container-apps-deploymentgit clone --depth 1 https://github.com/DanWahlin/github-azure-agentic-journeysWrote 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/danwahlin/github-azure-agentic-journeys/container-apps-deployment)<a href="https://agentmods.dev/skills/danwahlin/github-azure-agentic-journeys/container-apps-deployment"><img src="https://agentmods.dev/badge/skills/danwahlin/github-azure-agentic-journeys/container-apps-deployment.svg" alt="Measured on agentmods" 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.00124 | $0.02283 |
| Opus 5 | $0.00062 | $0.01141 |
| Sonnet 5 | $0.00025 | $0.00457 |
| Haiku 4.5 | $0.00012 | $0.00228 |
Grade A, and why
container-apps-deployment scanned grade A with 1 finding 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 6d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
Use `postprovision` for steps that need infrastructure outputs, such as setting `WEBHOOK_URL`. Use `postdeploy` for steps that need deployed services, such as rebuilding a frontend with its API URL. Hook code must invoke Copies of this mod
1 near-identical copy found in the catalogue:
- container-apps-deployment — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Container Apps Deployment Patterns
Supplements the official azure-prepare plugin skill with additional gotchas for Container Apps deployments — zone redundancy, azure.yaml, and SPA frontend patterns.
📖 ACR authentication: Use a deterministic two-phase pattern with separate deployment modules. The bootstrap module provisions each Container App with a public placeholder image and system-assigned identity but no
configuration.registriesentry. Grant that principalAcrPull, then make a later module depend on the role assignment and update the same app with the ACR login server andidentity: 'system'before deploying private images. A single module that declares both a new system identity and registry is not two-phase and can fail with an ACR token-exchange 401. Some azd versions callaz containerapp registry setautomatically and some do not. Never assume that implicit step occurred; verify the registry configuration before the first private-image deployment.
Region-Specific Gotchas
Container Apps Environment zoneRedundant
The AVM module br/public:avm/res/app/managed-environment may default zoneRedundant to true. Several regions (including westus) don't support it.
module cae 'br/public:avm/res/app/managed-environment:0.8.1' = {
params: {
// ...
zoneRedundant: false // Required for westus and other regions without zone support
}
}
Without this: azd up fails with "Zone redundancy is not currently supported in this region".
azure.yaml Configuration
Docker services require language field
azd requires either language or image on each service, even when docker.path is specified:
services:
api:
host: containerapp
language: ts # REQUIRED — azd won't infer from Dockerfile
docker:
path: api/Dockerfile
context: api
remoteBuild: true
Declare each service whose image azd owns this way. AIMarket declares only api; Bicep creates its web Container App and the project postdeploy hook owns the storefront ACR build and update. Without language: azd up fails with "must specify language or image". Without remoteBuild: true: azd can require a local Docker daemon.
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.
- 6d ago First seen · 178 lines · 124 tokens per session scan A 5895edb85d60
container-apps-deployment is a skill published in the GitHub repository DanWahlin/github-azure-agentic-journeys (37 stars, last pushed 1mo ago), licensed MIT. It adds 124 tokens to every session and 2,283 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
azure-prepare
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd…
azure-cloud-migrate
Assess and migrate cross-cloud workloads to Azure with reports and code conversion. Supports Lambda→Functions, Beanstalk/Heroku/App Engine→App Service, Fargate/Kubernetes/Cloud Run/Spring Boot→Container Apps. WHEN: migrate Lambda to Functions, AWS to Azure, migrate Beanstalk, migrate Heroku, migrate App Engine, Cloud…
azure-prepare
WORKFLOW SKILL — Prepare Azure apps for deployment (Bicep/Terraform, azure.yaml, Dockerfiles). WHEN: "create app", "build web app", "create API", "deploy to Azure", "generate Bicep", "generate Terraform", "function app", "add authentication", "managed identity". DO NOT USE FOR: cross-cloud migration…
kubernetes-basics
Core Kubernetes concepts including pods, deployments, services, and common troubleshooting patterns.
aws-cli
CLI-first AWS orchestration skill for Lambda, ECS/Fargate, and S3 workflows rooted in .☁️ runbooks.
flow-nexus-swarm
Cloud-based AI swarm deployment and event-driven workflow automation with Flow Nexus platform.