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-resource-organizationgit 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-resource-organization)<a href="https://agentmods.dev/skills/janegilring/awesome-azure-landing-zones/caf-resource-organization"><img src="https://agentmods.dev/badge/skills/janegilring/awesome-azure-landing-zones/caf-resource-organization/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-resource-organization"><img src="https://agentmods.dev/badge/skills/janegilring/awesome-azure-landing-zones/caf-resource-organization.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.00165 | $0.01050 |
| Opus 5 | $0.00082 | $0.00525 |
| Sonnet 5 | $0.00033 | $0.00210 |
| Haiku 4.5 | $0.00016 | $0.00105 |
Grade A, and why
caf-resource-organization 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resource organization
Overview
Resource organization defines the management group hierarchy and subscription strategy that everything else hangs off — governance, security, networking, and cost all attach to this scaffold. ALZ follows subscription democratization: subscriptions are the primary unit of management and scale, handed to workload teams as managed environments rather than treated as scarce. Design the hierarchy for policy inheritance and operational clarity, not to mirror the org chart.
When to use this skill
- Designing the management group hierarchy for a new or evolving landing zone.
- Deciding the subscription strategy (per workload, per environment, per business unit).
- Placing platform vs application subscriptions (Connectivity, Identity, Management; Corp, Online).
- Defining naming and tagging conventions for consistent organization and cost reporting.
- Reviewing an existing flat/ad-hoc structure against the conceptual ALZ architecture.
Key concepts
- Conceptual ALZ management groups (under the Intermediate root):
- Platform — shared services, with child groups Connectivity, Identity, Management.
- Landing Zones — application workloads, commonly split into Corp (private/hybrid) and Online (internet-facing).
- Decommissioned — subscriptions being retired (cancelled, policy-constrained).
- Sandbox — loosely governed space for experimentation, isolated from production.
- Subscription democratization — each workload (often per environment) gets its own subscription, used as a scale unit and management boundary.
- Management group depth — keep the hierarchy shallow (Azure supports up to 6 levels below root; ALZ rarely needs more than 3–4). Avoid mirroring the org chart.
- Naming and tagging — conventions that make resources identifiable and costs attributable (environment, owner, cost center, workload).
Decision guidance
Management group hierarchy
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 · 82 lines · 165 tokens per session scan A eb58d9f75975
caf-resource-organization is a skill published in the GitHub repository janegilring/awesome-azure-landing-zones (3 stars, last pushed 2mo ago), licensed MIT. It adds 165 tokens to every session and 1,050 once invoked, about $0.0008 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
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…