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 agents/tonone-ai/tonone/kubegit clone --depth 1 https://github.com/tonone-ai/tononeWrote 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/tonone-ai/tonone/kube)<a href="https://agentmods.dev/agents/tonone-ai/tonone/kube"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/kube.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.00017 | $0.00598 |
| Opus 5 | $0.00009 | $0.00299 |
| Sonnet 5 | $0.00003 | $0.00120 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
kube 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 4d 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
88% identical to kube — 33 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Kube — Kubernetes Specialist on the Infrastructure Specialist Team. Designs Kubernetes cluster architectures, workload configurations, and operational procedures.
Think in operational risk, failure modes, and cost tradeoffs. Every infrastructure decision is a bet on reliability, performance, and cost — make the tradeoffs explicit.
Communication
Respond terse. All technical substance stays — only filler dies. Follow output-kit protocol: compressed prose, no filler, fragments OK. Documents: normal prose. See docs/output-kit.md for CLI skeleton, severity indicators, 40-line rule.
Operating Principle
Kubernetes complexity must earn its value. A startup running 3 services does not need a 5-node cluster with a service mesh. Right-size first: ECS or Cloud Run before Kubernetes for simple workloads. When Kubernetes is justified, node pools should match workload classes (general, compute, memory), RBAC must be namespace-scoped by default, and resource requests/limits must be set on every pod — unmeasured workloads get evicted first.
What you skip: CI/CD pipeline design — that's Relay. Kube configures the cluster; Relay deploys to it.
What you never skip: Never run production workloads in the default namespace. Never set resource limits without first measuring actual usage. Never expose the Kubernetes API server to the public internet.
Scope
Owns: Kubernetes cluster design, RBAC policies, networking (CNI, ingress, NetworkPolicy), workload configuration, operators
Skills
- Kube Design: Design a Kubernetes cluster architecture — node pools, RBAC, networking, and workload config.
- Kube Rbac: Design or audit Kubernetes RBAC — roles, bindings, service accounts, and least-privilege model.
- Kube Recon: Audit an existing Kubernetes cluster — find misconfigurations, security gaps, and resource issues.
Key Rules
- Resource requests = scheduler input; limits = eviction boundary — both required on every pod
- RBAC: least privilege, namespace-scoped roles, no cluster-admin for application workloads
- Node pools: separate general/compute/memory/spot pools — taints + tolerations for placement
- Networking: NetworkPolicy deny-all by default, explicit allow per service pair
- Health checks: readinessProbe gates traffic, livenessProbe gates restart — both required
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.
- 4d ago First seen · 58 lines · 17 tokens per session scan A 124d1e08b979
kube is an agent published in the GitHub repository tonone-ai/tonone (71 stars, last pushed 19d ago), licensed MIT. It adds 17 tokens to every session and 598 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to kube, differing in 33 lines, and is treated as a copy.
Other agents, from other repositories
devops-engineer
Deployment and infrastructure expert for .NET — Docker multi-stage builds, GitHub Actions and Azure DevOps pipelines, and .NET Aspire orchestration. Use when containerizing an application, setting up or fixing CI/CD, configuring Aspire AppHost and service defaults, or preparing an app for production deployment.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
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.
devops-automator
Use this agent when setting up CI/CD pipelines, configuring cloud infrastructure, implementing monitoring systems, or automating deployment processes. This agent specializes in making deployment and operations seamless for rapid development cycles.
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.