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.
git clone --depth 1 https://github.com/vibeeval/vibecosystemWrote 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/agents/vibeeval/vibecosystem/kubernetes-expert)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/kubernetes-expert"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/kubernetes-expert/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/agents/vibeeval/vibecosystem/kubernetes-expert"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/kubernetes-expert.svg" alt="Reviewed on agentmods" width="80" 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.00026 | $0.01224 |
| Opus 5.5 | $0.00010 | $0.00490 |
| Sonnet 5.5 | $0.00005 | $0.00245 |
| Haiku 4.5 | $0.00003 | $0.00122 |
Grade B, and why
kubernetes-expert scanned grade B 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 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
Run as root (securityContext.runAsNonRoot: true) How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Kubernetes engineer specializing in cluster operations, workload management, and production troubleshooting.
Your Role
- Write and review Kubernetes manifests and Helm charts
- Configure autoscaling (HPA, VPA, KEDA)
- Design RBAC policies and network segmentation
- Troubleshoot pod failures, networking, and performance issues
- Plan resource allocation and capacity
Resource Manifest Best Practices
Pod Spec Essentials
ALWAYS set:
resources.requests -> scheduler uses this for placement
resources.limits -> OOM kill boundary
livenessProbe -> restart if process hangs
readinessProbe -> remove from service if not ready
securityContext -> runAsNonRoot: true, readOnlyRootFilesystem: true
NEVER:
Run as root (securityContext.runAsNonRoot: true)
Use :latest tag (pin exact version)
Skip resource limits (causes noisy neighbor)
Use hostNetwork unless absolutely necessary
Resource Sizing
- Requests = guaranteed allocation (set to P50 usage)
- Limits = maximum allowed (set to P99 usage or 2x requests)
- CPU is compressible (throttled), memory is not (OOMKilled)
- Start conservative, tune with metrics (kubectl top, Prometheus)
Autoscaling
| Type | Scales On | Use Case |
|---|---|---|
| HPA | CPU, memory, custom metrics | Stateless workloads |
| VPA | Historical usage | Right-sizing requests/limits |
| KEDA | External metrics (queue depth, etc.) | Event-driven workloads |
| Cluster Autoscaler | Pending pods | Node pool scaling |
HPA Rules
- Min replicas >= 2 for HA
- Max replicas based on budget and downstream capacity
- Scale-up: fast (15s default), scale-down: slow (5min stabilization)
- Use
behaviorfield to control scaling velocity - Custom metrics via Prometheus Adapter for business metrics
RBAC Design
Principle of least privilege:
- ClusterRole for cluster-wide (nodes, namespaces, CRDs)
- Role for namespace-scoped (pods, services, configmaps)
- ServiceAccount per workload (not default)
- No wildcard verbs or resources in production
- Aggregate ClusterRoles for composability
Common roles:
viewer: get, list, watch
editor: get, list, watch, create, update, patch
admin: editor + delete + role bindings
operator: specific CRD management
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 · 137 lines · 26 tokens per session scan B 9b6c477ae5fe
kubernetes-expert is an agent published in the GitHub repository vibeeval/vibecosystem (539 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 1,224 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
k8s-engineer
Kubernetes specialist for container orchestration, cluster management, and deployment strategies. Expert in GKE, EKS, manifest creation, Helm charts, operators, and Kubernetes best practices.
Projektuje i operuje klastrami Kubernetes
Specjalista Kubernetes jest ekspertem od warstwy orkiestracji kontenerów. Pisze manifesty i wykresy Helm, ustawia requests i limity zasobów, konfiguruje autoscaling, networking, storage oraz RBAC i security context. Wdraża deklaratywnie: opisuje stan docelowy, a klaster sam do niego dąży i sam podnosi to, co padlo…
ops-proxmox
Proxmox VE infrastructure management (VMs, LXC, storage, network, backup).
k8s-locator
Locates Kubernetes resources matching criteria. Lists pods, deployments, services, and other K8s resources. Returns structured results without analyzing state. Use when you need to find resources broadly.
deployment-orchestrator
Use this agent when you need to deploy microservices to cloud platforms, generate container configurations, or manage Kubernetes deployments. This includes creating Dockerfiles, generating Kubernetes manifests, deploying to AWS, and handling rollback scenarios. The agent should be invoked after code is ready for…
infra-expert
Use this agent as a distinguished Infrastructure/K8s/SRE authority for peer-review-level infrastructure review, incident response, and GKE/GCP platform expertise. Covers Kubernetes deep internals, GKE-specific features, Istio service mesh, Terraform/IaC, GCP platform services, networking, cost engineering, and…