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 gcp-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/gcp-landing-zone-setup)<a href="https://agentmods.dev/skills/selvarajmurugesan90/ops-engineering-skills/gcp-landing-zone-setup"><img src="https://agentmods.dev/badge/skills/selvarajmurugesan90/ops-engineering-skills/gcp-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/gcp-landing-zone-setup"><img src="https://agentmods.dev/badge/skills/selvarajmurugesan90/ops-engineering-skills/gcp-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.00100 | $0.02790 |
| Opus 5.5 | $0.00040 | $0.01116 |
| Sonnet 5.5 | $0.00020 | $0.00558 |
| Haiku 4.5 | $0.00010 | $0.00279 |
Grade A, and why
gcp-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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GCP Landing Zone Setup
Purpose
GCP's isolation boundary is the project — cheap to create, billed independently, but with no inherent hierarchy unless one is imposed through Resource Manager folders. Without a landing zone, organizations accumulate hundreds of ungoverned projects with inconsistent Organization Policies, no shared VPC, and IAM bindings granted directly at the project level with no audit trail of why. This skill defines a landing zone aligned to Google's enterprise foundations blueprint: a folder hierarchy that encodes environment and business-unit boundaries, Organization Policy constraints enforced top-down, Shared VPC for centralized networking, and a repeatable project-vending factory — so new projects are compliant and network-connected the moment they're created.
When to use
- Standing up a brand-new Google Cloud Organization or bringing ungoverned projects under Resource Manager folder control.
- Designing the folder hierarchy and deciding which Organization Policy constraints apply at which folder level.
- Onboarding a new team, product, or environment as a GCP project.
- Migrating from ad hoc project creation to the Terraform-based project
factory pattern (
terraform-google-modules/project-factory). - Auditing an existing organization for projects that sit outside any folder governance, or for Organization Policy drift.
Prerequisites & environment
- Organization Admin (
roles/resourcemanager.organizationAdmin) or equivalent custom role at the Organization node to create folders and Organization Policies. - A Cloud Identity or Google Workspace domain already established (GCP Organizations are anchored to one of these) and Google Groups modeled for IAM binding (never bind IAM directly to individual user accounts in a landing zone).
gcloudCLI ≥ 470.0.0 and Terraform ≥ 1.5 with thegoogle/google-betaproviders ≥ 5.x if using IaC — the project-factory and folder modules track provider versions closely; pin them.- A billing account (or multiple, if business units are billed
separately) and rights to link projects to it
(
roles/billing.userat minimum). - Decide the network model up front: Shared VPC (host project owns the VPC, service projects attach to it — the default recommendation) vs. VPC Network Peering between independent VPCs (only when workloads genuinely need separate network admin boundaries).
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 · 270 lines · 100 tokens per session scan A 17070f8911b4
gcp-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 100 tokens to every session and 2,790 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".