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 oci-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/oci-landing-zone-setup)<a href="https://agentmods.dev/skills/selvarajmurugesan90/ops-engineering-skills/oci-landing-zone-setup"><img src="https://agentmods.dev/badge/skills/selvarajmurugesan90/ops-engineering-skills/oci-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/oci-landing-zone-setup"><img src="https://agentmods.dev/badge/skills/selvarajmurugesan90/ops-engineering-skills/oci-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.00123 | $0.04295 |
| Opus 5.5 | $0.00049 | $0.01718 |
| Sonnet 5.5 | $0.00025 | $0.00859 |
| Haiku 4.5 | $0.00012 | $0.00430 |
Grade A, and why
oci-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 — 400 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OCI Landing Zone Setup
Purpose
OCI has no separate-account model like AWS or GCP-project model — a single
tenancy is the entire organization, and everything inside it is
organized by Compartments, a hierarchical logical container that is
simultaneously the OU-equivalent grouping construct and the place
resources actually live. Get the compartment design wrong and every
workload ends up flat in the root compartment with IAM policies that can't
be scoped cleanly, no separation between security tooling and application
resources, and no way to delegate administration without granting
tenancy-wide access. This skill defines a landing zone aligned to Oracle's
CIS OCI Landing Zone reference architecture: a compartment hierarchy
that encodes environment/function boundaries, IAM policies written in
OCI's plain-language policy grammar and scoped per compartment, Identity
Domains for identity isolation, Cloud Guard and Security Zones for
guardrail enforcement, and a hub network built on the Dynamic Routing
Gateway (DRG) — so new workloads land compliant and network-connected from
the first terraform apply.
When to use
- Standing up a brand-new OCI tenancy or bringing an ungoverned "everything in the root compartment" tenancy under proper compartment governance.
- Designing the compartment hierarchy and deciding which IAM policies, Cloud Guard targets, and Security Zone recipes apply at which compartment level.
- Onboarding a new team, product, or environment as an OCI compartment.
- Implementing or migrating to Oracle's CIS OCI Landing Zone Terraform reference architecture instead of hand-rolled, console-managed compartments and policies.
- Setting up Identity Domains for isolated identity realms (e.g. a separate domain for external partner or B2C access) rather than overloading the default domain.
- Auditing an existing tenancy for compartment drift, over-broad policies attached at the tenancy (root) level, or resources sitting directly in a parent compartment instead of a purpose-built leaf compartment.
- Explaining how OCI's tenancy/compartment/Identity Domain model maps to (and differs from) AWS Organizations/OUs, Azure Management Groups/subscriptions, or GCP folders/projects.
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 · 400 lines · 123 tokens per session scan A da0f5f540dd2
oci-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 123 tokens to every session and 4,295 once invoked, about $0.0005 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".