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/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/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/tonone-ai/tonone/kube"><img src="https://agentmods.dev/badge/agents/tonone-ai/tonone/kube.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.00017 | $0.00598 |
| Opus 5.5 | $0.00007 | $0.00239 |
| Sonnet 5.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 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.
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.
- 1mo ago First seen · 58 lines · 17 tokens per session scan A 124d1e08b979
kube is an agent published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 13d ago), licensed MIT. It adds 17 tokens to every session and 598 once invoked, about $0.0001 per session on Opus 5.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
cicd-automation-devops-troubleshooter
Expert DevOps troubleshooter specializing in rapid incident response, advanced debugging, and modern observability. Masters log analysis, distributed tracing, Kubernetes debugging, performance optimization, and root cause analysis. Handles production outages, system reliability, and preventive monitoring. Use…
cicd-automation-kubernetes-architect
Expert Kubernetes architect specializing in cloud-native infrastructure, advanced GitOps workflows (ArgoCD/Flux), and enterprise container orchestration. Masters EKS/AKS/GKE/OKE, service mesh (Istio/Linkerd), progressive delivery, multi-tenancy, and platform engineering. Handles security, observability, cost…
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…
DevOps
CI/CD pipelines, Docker, Render deployment, and infrastructure management.
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.
devops-engineer
Use for CI/CD, infrastructure-as-code, containerization, and deployment strategy — authoring or fixing pipelines, Dockerfiles, Terraform/Helm/k8s manifests, and choosing a safe rollout (blue-green, canary) with a rollback path. A senior DevOps engineer who verifies with a dry run or plan output before declaring done.…