Borrowing it
Nothing to install: this file belongs to nubenetes/awesome-kubernetes. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nubenetes/awesome-kubernetes/master/CLAUDE.mdgit clone --depth 1 https://github.com/nubenetes/awesome-kubernetesWrote 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/instructions/nubenetes/awesome-kubernetes/claude-md)<a href="https://agentmods.dev/instructions/nubenetes/awesome-kubernetes/claude-md"><img src="https://agentmods.dev/badge/instructions/nubenetes/awesome-kubernetes/claude-md.svg" alt="Measured on agentmods" 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.01242 | $0.01242 |
| Opus 5 | $0.00621 | $0.00621 |
| Sonnet 5 | $0.00248 | $0.00248 |
| Haiku 4.5 | $0.00124 | $0.00124 |
Grade A, and why
awesome-kubernetes 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 9d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — Nubenetes Project Instructions for Claude Code
Git Workflow: Gitflow
This repository uses Gitflow. All agents MUST follow this branching model:
Branches
master— Production. Only receives merges from release branches. Every merge to master gets a tag and a GitHub Release.develop— Integration branch. All feature branches merge here first.feat/*— Feature branches. Created fromdevelop, merged back todevelopvia PR.release/vX.Y.Z— Release branches. Created fromdevelopwhen ready to release, merged to bothmasterAND back todevelop.gh-pages— Deployment. Never touch directly.
Release Process (mandatory for all releases)
- Create feature branch from
develop:git checkout -b feat/description develop - Implement changes, commit, push feature branch
- Create PR:
gh pr create --base develop --head feat/description - Merge PR to develop:
gh pr merge N --merge - Create release branch:
git checkout -b release/vX.Y.Z develop - Merge release to master:
git checkout master && git merge release/vX.Y.Z --no-ff - Tag:
git tag -a vX.Y.Z -m "description" - Push master + tag:
git push origin master && git push origin vX.Y.Z - Back-merge master to develop:
git checkout develop && git merge master --no-ff && git push origin develop - Create GitHub Release:
gh release create vX.Y.Z --title "..." --notes "..."
Versioning
- Current:
v2.9.2 - Format:
v{major}.{minor}.{patch} - Major: breaking changes or architectural shifts
- Minor: new features (like the digest engine, new modules)
- Patch: bug fixes, config tweaks
Protected Branches
master, develop, and gh-pages are NEVER deleted. Branch cleanup runs bi-monthly for merged feature branches.
Repository Structure
Key Directories
docs/— V1 source (exhaustive archive, source of truth)v2-docs/— V2 source (AI-curated elite portal, derived from V1)src/— Python pipeline source codedata/— Inventory (YAML + SQL), config files, digest JSONscripts/— Utility scripts (backfill, etc.).github/workflows/— CI/CD (15 workflows)
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.
- 9d ago First seen · 94 lines · 1,242 tokens per session scan A fd919a5a62ef
awesome-kubernetes CLAUDE.md is an instructions file published in the GitHub repository nubenetes/awesome-kubernetes (669 stars, last pushed today), licensed Apache-2.0. It adds 1,242 tokens to every session, about $0.0062 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.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.