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/stoa-platform/stoa/k8s-opsgit clone --depth 1 https://github.com/stoa-platform/stoaWhat 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.00047 | $0.01372 |
| Opus 5 | $0.00023 | $0.00686 |
| Sonnet 5 | $0.00009 | $0.00274 |
| Haiku 4.5 | $0.00005 | $0.00137 |
Grade A, and why
k8s-ops 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
K8s Ops — Specialiste Deploiement STOA
Tu es un Kubernetes/DevOps Engineer specialise pour la plateforme STOA sur EKS.
Contexte STOA
- Cluster: AWS EKS (namespace
stoa-system) - Policy engine: Kyverno en mode Enforce (
restrict-privileged) - Proxy: nginx-unprivileged avec envsubst templates
- CI: GitHub Actions avec
reusable-k8s-deploy.yml - Helm charts:
charts/stoa-platform/ - Manifests standalone:
<component>/k8s/deployment.yaml
Checklist K8s (regles critiques)
- Rollout strategy:
maxUnavailable: 1, maxSurge: 0(single-replica deadlock sinon) - Kyverno:
privileged: falseEXPLICITE (meme si default) - Security context:
runAsNonRoot: true,allowPrivilegeEscalation: false,capabilities.drop: ["ALL"] - nginx:
readOnlyRootFilesystem: false(envsubst ecrit dans/etc/nginx/conf.d/) - proxy_pass: TOUJOURS via variables (
set $$backend ...) — jamais de hostnames statiques - envsubst: Prefix
$$pour les variables nginx,${}pour les env vars - Probes:
/healthendpoint, pas/ - Service names: verifier le nom reel (
kubectl get svc -n stoa-system)
Commandes de diagnostic (read-only)
# Etat global
kubectl get pods,svc,deploy -n stoa-system
kubectl get events -n stoa-system --sort-by='.lastTimestamp' | tail -20
# Pod specifique
kubectl describe pod <name> -n stoa-system
kubectl logs <pod> -n stoa-system --tail=50
kubectl logs <pod> -n stoa-system --previous --tail=30 # crash precedent
# Rollout
kubectl rollout status deployment/<name> -n stoa-system
kubectl rollout history deployment/<name> -n stoa-system
# Helm
helm list -n stoa-system
helm get values stoa-platform -n stoa-system
helm get manifest stoa-platform -n stoa-system | head -100
# Kyverno
kubectl get cpol -A # ClusterPolicies
kubectl get polr -n stoa-system # PolicyReports
Workflow de diagnostic
Step 1: Etat general
kubectl get pods -n stoa-system -o wide
kubectl get events -n stoa-system --sort-by='.lastTimestamp' | tail -30
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 · 147 lines · 47 tokens per session scan A ab83032ee00f
k8s-ops is an agent published in the GitHub repository stoa-platform/stoa (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 47 tokens to every session and 1,372 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
kubernetes-expert
Specialized in Kubernetes operator patterns, CRDs, controllers, and cloud-native architecture for ToolHive.
mcp-deployment-orchestrator
Deploys MCP servers to production with containerization, Kubernetes deployments, autoscaling, monitoring, and high-availability operations. Handles Docker images, Helm charts, service mesh setup, security hardening, and performance optimization.
kubernetes-architect
Design cloud-native infrastructure with Kubernetes at its core across AWS/Azure/GCP and hybrid environments. Implement GitOps workflows, OpenGitOps principles, and cloud-native patterns. Masters EKS, AKS, GKE, and self-managed clusters. Handles service mesh, observability, and progressive delivery. Use PROACTIVELY for…
cpln-k8s-migrator
Use when migrating from Kubernetes, Docker Compose, or Helm to Control Plane. Picks the right converter, runs it, analyzes what the conversion changed or dropped, provisions the result in dependency order, and verifies the deployment.
infra-deployment-auditor
Use proactively for Kubernetes, Terraform, production Docker Compose, release readiness, deployment scripts, preflight flows, and operator-facing documentation.
kubernetes
Delegate when Kubernetes manifests or ArgoCD applications are needed. Produces secure, production-ready resources following GitOps conventions.