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 janegilring/awesome-azure-landing-zones --skill caf-platform-automation-devopsgit clone --depth 1 https://github.com/janegilring/awesome-azure-landing-zonesWrote 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/janegilring/awesome-azure-landing-zones/caf-platform-automation-devops)<a href="https://agentmods.dev/skills/janegilring/awesome-azure-landing-zones/caf-platform-automation-devops"><img src="https://agentmods.dev/badge/skills/janegilring/awesome-azure-landing-zones/caf-platform-automation-devops/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/janegilring/awesome-azure-landing-zones/caf-platform-automation-devops"><img src="https://agentmods.dev/badge/skills/janegilring/awesome-azure-landing-zones/caf-platform-automation-devops.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.00208 | $0.01088 |
| Opus 5 | $0.00104 | $0.00544 |
| Sonnet 5 | $0.00042 | $0.00218 |
| Haiku 4.5 | $0.00021 | $0.00109 |
Grade A, and why
caf-platform-automation-devops 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 12d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platform automation and DevOps
Overview
This design area makes the platform repeatable and maintainable: the landing zone is defined as
infrastructure as code, deployed through CI/CD pipelines with secure, secretless automation
identities, and kept up to date as Azure and the ALZ reference implementations evolve. It is
IaC-agnostic at the design level — the practice (Git workflow, environments, identities, drift
control) matters more than the specific tool; tool-specific steps live in the alz-accelerator
skill.
When to use this skill
- Defining the IaC strategy and repository/branching model for the platform.
- Designing CI/CD pipelines (GitHub Actions or Azure DevOps) to deploy and update ALZ.
- Setting up automation identities with managed identity / workload identity federation (OIDC) instead of long-lived secrets.
- Planning environments and promotion (e.g. canary/management-group rings) and drift control.
- Establishing a process to keep the landing zone current with upstream module/policy updates.
Key concepts
- Platform as code — the management groups, policies, networking, and baselines are defined in source control, reviewed, and deployed via pipelines — not click-ops.
- Bootstrap — the one-time setup of the deployment toolchain (repos, pipelines, service connections, deployment identity) before the platform itself is deployed.
- Workload identity federation (OIDC) — pipelines authenticate to Azure with short-lived, federated tokens; no stored secrets to rotate or leak.
- Environments / promotion — change flows through stages (plan → review → apply), often using management-group rings to limit blast radius.
- Drift and updates — detect configuration drift and consume upstream improvements (modules, AVM, default policies) on a maintained cadence (keep ALZ up to date).
Decision guidance
IaC and repository design
- Treat the platform as a versioned product: one source of truth, reviewed pull requests, tagged releases. Separate platform from workload pipelines.
- Pick the IaC tool that matches team skills and the chosen accelerator (Bicep or Terraform) — keep
the practice consistent regardless (see
alz-acceleratorfor specifics).
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.
- 12d ago First seen · 81 lines · 208 tokens per session scan A a7338fec615d
caf-platform-automation-devops is a skill published in the GitHub repository janegilring/awesome-azure-landing-zones (3 stars, last pushed 2mo ago), licensed MIT. It adds 208 tokens to every session and 1,088 once invoked, about $0.0010 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
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.