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 agentmods add instructions/htrixtec/mcp-server-kubernetes/claude-mdgit clone --depth 1 https://github.com/htrixtec/mcp-server-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/htrixtec/mcp-server-kubernetes/claude-md)<a href="https://agentmods.dev/instructions/htrixtec/mcp-server-kubernetes/claude-md"><img src="https://agentmods.dev/badge/instructions/htrixtec/mcp-server-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 | $0.00828 | $0.00828 |
| Opus 5 | $0.00414 | $0.00414 |
| Sonnet 5 | $0.00166 | $0.00166 |
| Haiku 4.5 | $0.00083 | $0.00083 |
Grade C, and why
mcp-server-kubernetes CLAUDE.md scanned grade C with 1 finding 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 3d 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
- Server loads kubeconfig from multiple sources: KUBECONFIG_YAML env var, KUBECONFIG path, or ~/.kube/config This is a copy
100% identical to kube-mcp CLAUDE.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 91 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.
Development Commands
Build and Development
bun run build- Compile TypeScript to dist/ and make executablesbun run dev- Start TypeScript compiler in watch mode for developmentbun run start- Run the compiled server from dist/index.jsbun run test- Run all tests using Vitest
Testing and Quality
bun run test- Execute the complete test suite with custom sequencer (kubectl tests run last)- Tests have 120s timeout and 60s hook timeout due to Kubernetes operations
- Use
npx @modelcontextprotocol/inspector node dist/index.jsfor local testing with Inspector - Always run single test based on with area you are working on. running all tests will take a long time.
Local Development Testing
bun run chat- Test locally with mcp-chat CLI client- For Claude Desktop testing, point to local
dist/index.jsbuild
Architecture Overview
This is an MCP (Model Context Protocol) server that provides Kubernetes cluster management capabilities. The server connects to Kubernetes clusters via kubectl and offers both read-only and destructive operations.
Core Components
KubernetesManager (src/utils/kubernetes-manager.ts): Central class managing Kubernetes API connections, resource tracking, port forwards, and watches. Handles kubeconfig loading from multiple sources in priority order.
Tool Structure: Each Kubernetes operation is implemented as a separate tool in src/tools/, with corresponding Zod schemas for validation. Tools are divided into:
- kubectl operations (get, describe, apply, delete, create, etc.)
- Helm operations (install, upgrade, uninstall charts)
- Specialized operations (port forwarding, scaling, rollouts)
Resource Handlers (src/resources/handlers.ts): Manage MCP resource endpoints for dynamic data retrieval.
Configuration System (src/config/): Contains schemas and templates for deployments, namespaces, containers, and cleanup operations.
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.
- 3d ago First seen · 91 lines · 828 tokens per session scan C 5ed32f344ceb
mcp-server-kubernetes CLAUDE.md is an instructions file published in the GitHub repository htrixtec/mcp-server-kubernetes (0 stars, last pushed 2mo ago), licensed MIT. It adds 828 tokens to every session, about $0.0041 per session on Opus 5. A static security scan graded it C with 1 finding (reaches for credential files). It is 100% identical to kube-mcp CLAUDE.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
appwrite AGENTS.md
AGENTS.md instructions for appwrite/appwrite, covering appwrite, commands, stack, layout and libraries.
openlakeforge AGENTS.md
Instructions for malon64/openlakeforge, covering agent and contributor guide, what this project is, orientation — read in this order, repository map and architectural rules.
docker-zoneminder CLAUDE.md
Instructions for jantman/docker-zoneminder, covering claude.md, project overview, build and test, ci/cd and architecture.
mitos CLAUDE.md
Instructions for mitos-run/mitos, covering claude.md, project overview, operating principles, commands and architecture.
observability-mcp CLAUDE.md
Instructions for ThoTischner/observability-mcp, covering observability-mcp development guide, docker-first development, quick start, rebuild a single service and view logs.
workshop copilot-instructions.md
Copilot instructions for canonical/workshop, covering github copilot instructions, project overview, tech stack, repository structure and core directories.