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 selvarajmurugesan90/ops-engineering-skills --skill aws-landing-zone-setupgit clone --depth 1 https://github.com/selvarajmurugesan90/ops-engineering-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/selvarajmurugesan90/ops-engineering-skills/aws-landing-zone-setup)<a href="https://agentmods.dev/skills/selvarajmurugesan90/ops-engineering-skills/aws-landing-zone-setup"><img src="https://agentmods.dev/badge/skills/selvarajmurugesan90/ops-engineering-skills/aws-landing-zone-setup/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/selvarajmurugesan90/ops-engineering-skills/aws-landing-zone-setup"><img src="https://agentmods.dev/badge/skills/selvarajmurugesan90/ops-engineering-skills/aws-landing-zone-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00104 | $0.02715 |
| Opus 5.5 | $0.00042 | $0.01086 |
| Sonnet 5.5 | $0.00021 | $0.00543 |
| Haiku 4.5 | $0.00010 | $0.00271 |
Grade A, and why
aws-landing-zone-setup 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 1mo 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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Landing Zone Setup
Purpose
A landing zone is the multi-account foundation an organization builds once and every application team builds on top of afterward: account structure, identity, network, logging, and guardrails. Getting it wrong is expensive to unwind — teams end up with flat single-account sprawl, inconsistent tagging, no centralized audit trail, and no policy enforcement boundary between "sandbox" and "production." This skill defines a repeatable, Control-Tower-based AWS landing zone so new accounts are vended consistently, guardrails are enforced at the Organizational Unit (OU) level instead of per-account, and security/audit teams get a single pane of glass without blocking developer velocity.
When to use
- Standing up AWS for a new organization or migrating off a single flat AWS account.
- Designing the OU hierarchy and deciding which Service Control Policies (SCPs) apply where.
- Onboarding a new business unit, environment, or acquired company into an existing AWS Organization.
- Reviewing/auditing an existing landing zone for drift (e.g. accounts created outside Control Tower, missing guardrails, orphaned root-level IAM users).
- Migrating from a hand-rolled multi-account setup to AWS Control Tower or Landing Zone Accelerator (LZA).
Prerequisites & environment
- An AWS Organization already exists or you have rights to create one
(
organizations:CreateOrganization) from a dedicated Management Account that runs no workloads. - AWS CLI v2 and, if using infrastructure-as-code, Terraform ≥ 1.5 (for the
awsprovider ≥ 5.x) or the AWS Landing Zone Accelerator (LZA) CDK toolchain. - Decide up front: Control Tower (AWS-managed, opinionated, fastest to start) vs. Landing Zone Accelerator (more customizable, config-as-code, used when you need FedRAMP/regulated-industry guardrails Control Tower doesn't ship out of the box) vs. fully custom Terraform (only for teams with deep multi-account IaC maturity already).
- Enable AWS IAM Identity Center (successor to AWS SSO) in the management account — Control Tower assumes it for federated human access.
- A registered root/parent domain or subdomain delegation if you plan per-account Route 53 zones.
- Budget for the mandatory Control Tower resources: a Log Archive account and an Audit account are created automatically and incur S3/CloudTrail/ Config costs even when idle.
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.
- 1mo ago First seen · 266 lines · 104 tokens per session scan A da9f6734c86a
aws-landing-zone-setup is a skill published in the GitHub repository selvarajmurugesan90/ops-engineering-skills (42 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 104 tokens to every session and 2,715 once invoked, about $0.0004 per session on Opus 5.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-30.
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-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running security audits (auditcluster.sh), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (gVisor), enforcing Pod…
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 generating K8s YAML manifests (use gke-manifest-generation) or disaster recovery…
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…
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".