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/alexeyshishin/as-skill/devops-k8sgit clone --depth 1 https://github.com/alexeyshishin/as-skillWrote 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/alexeyshishin/as-skill/devops-k8s)<a href="https://agentmods.dev/agents/alexeyshishin/as-skill/devops-k8s"><img src="https://agentmods.dev/badge/agents/alexeyshishin/as-skill/devops-k8s.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 | $0.00055 | $0.00637 |
| Opus 5 | $0.00028 | $0.00318 |
| Sonnet 5 | $0.00011 | $0.00127 |
| Haiku 4.5 | $0.00006 | $0.00064 |
Grade A, and why
k8s-agent 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.
What it actually says
K8s Agent — Executing
Scope
k8s/**
Structure
k8s/
├── chatbot/
│ ├── base/ # Kustomize base (Deployment, Service, ConfigMap)
│ └── overlays/
│ ├── dev/ # dev patches
│ └── prod/ # prod patches (strict limits, HPA)
├── external-secret-operator/ # ESO CRDs, ClusterSecretStore, ExternalSecrets
└── ingress-controller/ # NGINX ingress config
Commands
# Preview
kubectl kustomize k8s/chatbot/overlays/dev
kubectl kustomize k8s/chatbot/overlays/prod
# Apply (dev/staging by hand only)
kubectl apply -k k8s/chatbot/overlays/dev
# Prod — only via ArgoCD
argocd app sync <app-name>
argocd app get <app-name>
# Validate manifests
kubectl kustomize . | kubectl apply --dry-run=server -f -
kube-linter lint .
# Change context
kubectx dev
kubectx prod
# All contexts
kubectx
ESO pattern
apiVersion: external-secrets.io/v1beta1
kind: ExternalSecret
metadata:
name: <name>
spec:
secretStoreRef:
name: vault-backend
kind: ClusterSecretStore
refreshInterval: 1h
target:
name: <k8s-secret-name>
creationPolicy: Owner
data:
- secretKey: <key>
remoteRef:
key: <vault/path>
property: <vault-key>
ArgoCD ApplicationSet pattern
apiVersion: argoproj.io/v1alpha1
kind: ApplicationSet
spec:
generators:
- list:
elements:
- name: <app>
namespace: <ns>
template:
spec:
source:
repoURL: <git-url>
path: <kustomize-path>
syncPolicy:
automated:
prune: true
selfHeal: true
Rules
- Prod — ArgoCD only, never
kubectl applydirectly - Resource limits/requests are mandatory on ALL containers
- Secrets — only via ESO, never hardcoded in YAML
- Don't use deprecated API versions
latesttag in prod — forbidden- PDB for stateful and critical services
- Labels:
app,version,component,app.kubernetes.io/managed-by: kustomize
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 · 99 lines · 0 tokens per session scan A 33d19a391ffe
k8s-agent is an agent published in the GitHub repository alexeyshishin/as-skill (4 stars, last pushed 16d ago), licensed MIT. It adds 55 tokens to every session and 637 once invoked, about $0.0003 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
Kubernetes manifests, Helm charts, RBAC, HPA, network policies, and cluster troubleshooting specialist.
container-orchestration-expert
Use this agent when working with Docker, Kubernetes, or any container-related tasks including building Dockerfiles, creating docker-compose configurations, troubleshooting container deployments, optimizing container performance, designing container architectures, or needing guidance on containerization best practices.…
FAI Kubernetes Expert
Kubernetes specialist — pod scheduling, GPU resource management, network policies, Helm charts, GitOps with Flux/ArgoCD, and production-grade AI workload orchestration on AKS.
infra-specialist
Use for isolated Terraform, Docker, AWS, Azure, and deployment-documentation work across terraform/, aws/, docker-compose.yml, DEPLOYMENT.md, and agenticai/deployments/.
infra-deployment-auditor
Use proactively for Kubernetes, Terraform, production Docker Compose, release readiness, deployment scripts, preflight flows, and operator-facing documentation.
helm-config-validator
Validates Helm chart configurations across CPP environments. Detects secrets in values, missing environment overrides, configuration drift, and misconfigured resources. user: "Validate the Helm chart config for cpp-hearing across all environments" assistant: "I'll use the helm-config-validator agent to check for…