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 niels-emmer/myace --skill gcp-landing-zonesgit clone --depth 1 https://github.com/niels-emmer/myaceWrote 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/niels-emmer/myace/gcp-landing-zones)<a href="https://agentmods.dev/skills/niels-emmer/myace/gcp-landing-zones"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/gcp-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.
<a href="https://agentmods.dev/skills/niels-emmer/myace/gcp-landing-zones"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/gcp-landing-zones.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.00038 | $0.01134 |
| Opus 5 | $0.00019 | $0.00567 |
| Sonnet 5 | $0.00008 | $0.00227 |
| Haiku 4.5 | $0.00004 | $0.00113 |
Grade A, and why
GCP 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 8d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
The Google Cloud Adoption Framework (GCAF) is the set of practices for governing GCP at scale. This skill covers the governance essentials you need to design a landing zone that is secure, auditable, and cost-attributable — the resource hierarchy, folder/project design, IAM scoping, VPC topology, and Organization-policy guardrails. It deliberately does not reproduce the full landing-zone accelerator (Google Cloud's Enterprise Foundations blueprint / Cloud Foundation Toolkit); the accelerator is a reference for the complete, opinionated implementation, while this skill is the decision layer you apply to any GCP environment.
When to use it
When designing or reviewing a GCP environment's structure — a new project, a folder reorganization, an Organization-policy/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.
Resource hierarchy
- Use the hierarchy Organization → Folders → Projects → Resources, with IAM and Organization policies applied at each level and inherited down.
- Separate platform (bootstrap, networking, security, logging) from workload folders, so governance applied at the platform level inherits down without entangling workload-specific policy.
- Keep the hierarchy shallow and meaningful — a handful of folders, each with a clear purpose, not a deep tree that mirrors the org chart.
- Apply IAM and Organization policies 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'sexception-documentationskill).
Folder and project design
- Use projects as scale units and trust boundaries, not cost centers (cost attribution belongs to labels, not project boundaries).
- Group projects by environment/workload boundary (e.g. a
prod/nonprodsplit, or one per major workload) so blast radius and policy scope stay manageable. - Keep the bootstrap/organization project for organization-wide administration and shared infrastructure only — never run workloads in it. Use dedicated projects for shared services (logging, networking) and for each workload/environment.
- Avoid a single project for everything, and avoid one project per microservice — both extremes make governance either impossible or unmanageable.
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.
- 8d ago First seen · 103 lines · 38 tokens per session scan A d74cf51faf2a
GCP Landing Zones is a skill published in the GitHub repository niels-emmer/myace (1 stars, last pushed 5d ago), licensed MIT. It adds 38 tokens to every session and 1,134 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-09-03.
Other skills, from other repositories
implementing-gcp-organization-policy-constraints
Implement GCP Organization Policy constraints to enforce security guardrails across the entire resource hierarchy, restricting risky configurations and ensuring compliance at organization, folder, and project levels.
Cloud Security & Container Hardening
AWS/Azure/GCP security auditing, container and Kubernetes hardening, Infrastructure as Code scanning, and cloud compliance assessment.
loom-kubernetes
Kubernetes deployment, cluster architecture, security, and operations.
loom-prometheus
Prometheus monitoring and alerting for cloud-native observability.
loom-terraform
Infrastructure as Code with Terraform/OpenTofu.
loom-karpenter
Kubernetes node autoscaling and cost optimization with Karpenter.