AWS CAF Landing Zones

AWS CAF Landing Zones is a skill for Claude Code, Codex from niels-emmer/myace. It costs 36 tokens per session (1,066 once invoked), scanned A, original, MIT.

A guide to structuring large AWS environments using Organizations accounts, organizational units, access-control rules, identity permissions, and network layouts. AWS is Amazon’s cloud platform; a landing zone is its planned foundation for running many accounts and workloads.

In plain words
What is it for?
Use it to design or review AWS accounts, organizational-unit hierarchies, Service Control Policies, IAM permissions, and VPC network topology.
Why use it?
It helps teams establish consistent governance, security boundaries, auditing, and cost ownership before adding or reorganizing cloud workloads.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for aider. Also seen: mentions Codex; built for aider; mentions OpenCode.

Good fit Use it to design or review AWS accounts, organizational-unit hierarchies, Service Control Policies, IAM permissions, and VPC network topology.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/niels-emmer/myace/aws-caf-landing-zones
Install

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.

Any agent
npx skills add niels-emmer/myace --skill aws-caf-landing-zones
Clone the repo
git clone --depth 1 https://github.com/niels-emmer/myace

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for AWS CAF Landing Zones

README.md
[![agentmods](https://agentmods.dev/badge/skills/niels-emmer/myace/aws-caf-landing-zones/github.svg)](https://agentmods.dev/skills/niels-emmer/myace/aws-caf-landing-zones)
Your own site
<a href="https://agentmods.dev/skills/niels-emmer/myace/aws-caf-landing-zones"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/aws-caf-landing-zones/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.

agentmods 80×15 button for AWS CAF Landing Zones

Your own site · 80×15
<a href="https://agentmods.dev/skills/niels-emmer/myace/aws-caf-landing-zones"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/aws-caf-landing-zones.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,066 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00036 $0.01066
Opus 5 $0.00018 $0.00533
Sonnet 5 $0.00007 $0.00213
Haiku 4.5 $0.00004 $0.00107

Measured 12d ago against content hash bce914797685, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

AWS CAF Landing Zones 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.

collections/additional/aws/skills/aws-caf-landing-zones/SKILL.md · 94 lines

How it starts

The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Purpose

The AWS Cloud Adoption Framework (CAF) is the set of practices for governing AWS at scale. This skill covers the governance essentials you need to design a landing zone that is secure, auditable, and cost-attributable — AWS Organizations OU hierarchy, account design, Service Control Policies (SCPs), IAM scoping, and VPC topology. It deliberately does not reproduce the full landing-zone accelerator (AWS Control Tower / Landing Zone Accelerator); the accelerator is a reference for the complete, opinionated implementation, while this skill is the decision layer you apply to any AWS environment.

When to use it

When designing or reviewing an AWS environment's structure — a new account, an OU reorganization, an SCP/guardrail change, or a network-topology decision. Also before scaffolding a new workload into an existing landing zone, to confirm it fits the established pattern.

AWS Organizations OU hierarchy

  • Separate platform (management, connectivity, security) from workload OUs, so governance applied at the platform level inherits down without entangling workload-specific policy.
  • Keep the hierarchy shallow and meaningful — a handful of OUs, each with a clear purpose, not a deep tree that mirrors the org chart.
  • Apply SCPs and IAM at the highest level where it's uniformly correct, and let it inherit; override only where a genuine exception exists (and document it per iac-expert's exception-documentation skill).

Account design

  • Use accounts as scale units and trust boundaries, not cost centers (cost attribution belongs to tags, not account boundaries).
  • Group accounts by environment/workload boundary (e.g. a prod/nonprod split, or one per major workload) so blast radius and policy scope stay manageable.
  • Keep the management account for billing and organization-wide administration only — never run workloads in it. Use dedicated accounts for shared services (logging, networking) and for each workload/environment.
  • Avoid a single account for everything, and avoid one account per microservice — both extremes make governance either impossible or unmanageable.

Read the full file on GitHub · 94 lines

Changes

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.

  1. 12d ago First seen · 94 lines · 36 tokens per session scan A bce914797685

Subscribe to this mod's changes

AWS CAF Landing Zones is a skill published in the GitHub repository niels-emmer/myace (1 stars, last pushed 5d ago), licensed MIT. It adds 36 tokens to every session and 1,066 once invoked, about $0.0002 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.