cloud-native-ref CLAUDE.md

Repository instructions for a cloud platform reference project using AWS EKS, Google GKE, Kubernetes, and infrastructure tools. They describe the repository layout, architecture, and setup guidance for Claude Code.

In plain words
What is it for?
Use them when working on network, security, Kubernetes, GitOps, secrets, or cluster-bootstrap files in that repository.
Why use it?
They help an agent find the right working directories and follow the project's rules when changing infrastructure or platform components.

Instructions file

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.

agentmods
npx agentmods add instructions/smana/cloud-native-ref/claude-md
Clone the repo
git clone --depth 1 https://github.com/Smana/cloud-native-ref
Per session 5,497 This file is loaded in full into every session.
When invoked 5,497 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.05497 $0.05497
Opus 5 $0.02749 $0.02749
Sonnet 5 $0.01099 $0.01099
Haiku 4.5 $0.00550 $0.00550

Measured yesterday against content hash 0fac6c0b7164, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cloud-native-ref CLAUDE.md 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 yesterday.

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.

CLAUDE.md · 385 lines

How it starts

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

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Repository Overview

This is a comprehensive cloud-native platform reference repository implementing GitOps practices with Kubernetes. The repository demonstrates production-ready configurations for building, managing, and maintaining a secure, scalable cloud-native platform using AWS EKS and GCP GKE.

Infrastructure Architecture

The platform is deployed in three sequential stages:

  1. Network Layer (opentofu/aws/network/): VPC, subnets, Route53, and Tailscale VPN
  2. Security Layer (opentofu/aws/openbao/): OpenBao cluster for secrets management and PKI
  3. Kubernetes Layer (opentofu/aws/eks/init/ + opentofu/aws/eks/configure/): EKS cluster with Flux, Cilium, and Karpenter

Key Components

  • OpenTofu: Infrastructure as Code (Terraform alternative)
  • Terramate: OpenTofu orchestration and stack management
  • Flux: GitOps continuous delivery
  • Crossplane: Infrastructure composition from Kubernetes
  • OpenBao: Secrets management and private PKI
  • Cilium: Advanced networking and security with eBPF
  • Gateway API: Modern ingress and traffic routing
  • VictoriaMetrics: High-performance observability stack

EKS Bootstrap Architecture

Two-stage OpenTofu deployment: Stage 1 creates the EKS cluster with temporary CNI, Stage 2 replaces it with Cilium and installs Flux.

Why two stages? Helm provider needs cluster endpoint at plan time, so Stage 2 runs after the cluster exists.

Deploy: cd opentofu && terramate script run deploy — one command builds the whole platform, EKS included. cd opentofu/aws/eks/init && terramate script run deploy re-runs just this stack, e.g. after a failure.

Key Files:

  • opentofu/config.tm.hcl - Cilium/Flux versions
  • opentofu/aws/eks/init/main.tf - EKS module with bootstrap addons
  • opentofu/aws/eks/configure/main.tf - Cilium and Flux helm_releases
  • opentofu/aws/eks/init/helm_values/cilium.yaml - Cilium Helm values

Read the full file on GitHub · 385 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. yesterday First seen · 385 lines · 5,497 tokens per session scan A 0fac6c0b7164

Subscribe to this mod's changes

cloud-native-ref CLAUDE.md is an instructions file published in the GitHub repository Smana/cloud-native-ref (99 stars, last pushed yesterday), licensed Apache-2.0. It adds 5,497 tokens to every session, about $0.0275 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-30.

Related

Other instructions, from other repositories