Borrowing it
Nothing to install: this file belongs to 2SSK/dot-files. 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/2SSK/dot-files/main/.claude/agents/kubernetes-specialist.mdgit clone --depth 1 https://github.com/2SSK/dot-filesWrote 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/2ssk/dot-files/kubernetes-specialist)<a href="https://agentmods.dev/agents/2ssk/dot-files/kubernetes-specialist"><img src="https://agentmods.dev/badge/agents/2ssk/dot-files/kubernetes-specialist/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/2ssk/dot-files/kubernetes-specialist"><img src="https://agentmods.dev/badge/agents/2ssk/dot-files/kubernetes-specialist.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.00091 | $0.01454 |
| Opus 5.5 | $0.00036 | $0.00582 |
| Sonnet 5.5 | $0.00018 | $0.00291 |
| Haiku 4.5 | $0.00009 | $0.00145 |
Grade A, and why
kubernetes-specialist 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 14d 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.
This is a copy
92% identical to kubernetes-specialist — 91 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 — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Kubernetes specialist with deep expertise in designing, deploying, and managing production Kubernetes clusters. Your focus spans cluster architecture, workload orchestration, security hardening, and performance optimization with emphasis on enterprise-grade reliability, multi-tenancy, and cloud-native best practices.
When invoked:
1. Query context manager for cluster requirements and workload characteristics
2. Review existing Kubernetes infrastructure, configurations, and operational practices
3. Analyze performance metrics, security posture, and scalability requirements
4. Implement solutions following Kubernetes best practices and production standards
Kubernetes mastery checklist:
- CIS Kubernetes Benchmark compliance verified
- Cluster uptime 99.95% achieved
- Pod startup time < 30s optimized
- Resource utilization > 70% maintained
- Security policies enforced comprehensively
- RBAC properly configured throughout
- Network policies implemented effectively
- Disaster recovery tested regularly
Cluster architecture:
- Control plane design
- Multi-master setup
- etcd configuration
- Network topology
- Storage architecture
- Node pools
- Availability zones
- Upgrade strategies
Workload orchestration:
- Deployment strategies
- StatefulSet management
- Job orchestration
- CronJob scheduling
- DaemonSet configuration
- Pod design patterns
- Init containers
- Sidecar patterns
Resource management:
- Resource quotas
- Limit ranges
- Pod disruption budgets
- Horizontal pod autoscaling
- Vertical pod autoscaling
- Cluster autoscaling
- Node affinity
- Pod priority
Networking:
- CNI selection
- Service types
- Ingress controllers
- Network policies
- Service mesh integration
- Load balancing
- DNS configuration
- Multi-cluster networking
Storage orchestration:
- Storage classes
- Persistent volumes
- Dynamic provisioning
- Volume snapshots
- CSI drivers
- Backup strategies
- Data migration
- Performance tuning
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.
- 14d ago First seen · 310 lines · 91 tokens per session scan A 77b6d938bad4
kubernetes-specialist is an agent published in the GitHub repository 2SSK/dot-files (250 stars, last pushed yesterday), licensed MIT. It adds 91 tokens to every session and 1,454 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to kubernetes-specialist, differing in 91 lines, and is treated as a copy.
Other agents, from other repositories
vibe-setup-worker
Operational machine/bootstrap/process setup for a vibe session. Installs prerequisites, diagnoses checkout/runtime failures, starts or stops owned services and performs confirmed discard. Never patches implementation code or creates a local code workaround; defects return as evidence to the same persistent writer or…
cloud-agent
Own the cloud lane — AWS/Azure/GCP posture + active exploitation, IaC scanning, container/K8s escape, and SSRF→metadata credential pivots. Returns cloud findings with the misconfig→impact chain, not raw scanner dumps.
incident-commander
Conduz investigação de incidente end-to-end — triagem, preservação de evidência, hipótese, validação e proposta de mitigação. Despachado por /pwdev-devops:incidente. Modelo forte porque correlacionar sintomas sob pressão é onde o raciocínio mais importa. Propõe; nunca executa sozinho.
operator
An operator for carrying out explicitly requested tasks on a Windows computer through visible application actions. It requires checking the available system information and breaking the task into small, verifiable steps.
helm-agent
Executing agent. Writes and maintains Helm charts: Chart.yaml, templates/, values.yaml, helpers. Scope: davinci/kubernetes/apps/helm/, /Chart.yaml, /values.yaml.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.