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 skills add fmind/dot --skill kubernetesgit clone --depth 1 https://github.com/fmind/dotWrote 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/skills/fmind/dot/kubernetes)<a href="https://agentmods.dev/skills/fmind/dot/kubernetes"><img src="https://agentmods.dev/badge/skills/fmind/dot/kubernetes/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/skills/fmind/dot/kubernetes"><img src="https://agentmods.dev/badge/skills/fmind/dot/kubernetes.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.00022 | $0.00927 |
| Opus 5.5 | $0.00009 | $0.00371 |
| Sonnet 5.5 | $0.00004 | $0.00185 |
| Haiku 4.5 | $0.00002 | $0.00093 |
Grade A, and why
kubernetes 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 9d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kubernetes Cluster and Workload Operations
Use kubectl, helm, k9s, kustomize, and stern for Kubernetes cluster inspection, manifest authoring, Helm releases, and log debugging. docker manages container runtimes and infra-as-code provisions managed cloud clusters.
Confirm user authority for cluster mutations and spending, reusing existing authorization. Pin --context and --namespace (or Helm's --kube-context) after resolving the intended cluster.
Workflow
-
Verify active context and namespace: inspect the current cluster context before running any command; never assume terminal defaults point to dev.
kubectl config get-contexts kubectl --context <context> cluster-info -
Lint and validate manifests: validate schemas against the target cluster's version (kubeconform defaults to
masterschemas) and verify security practices prior to applying manifests.kubeconform -strict -summary -kubernetes-version <cluster-version> <file-or-directory> trivy config <file-or-directory> kustomize build <kustomization-dir> | kubeconform -strict -summary -kubernetes-version <cluster-version> - -
Use a local cluster only when needed: read k3d before creating or deleting one; manifest checks often answer the question without it.
-
Deploy declaratively: apply configurations using Helm or Kustomize; preview changes before mutating cluster state.
helm upgrade --install <release-name> <chart-path> --kube-context <context> --namespace <namespace> --dry-run=server --hide-secret kubectl --context <context> --namespace <namespace> diff -k <kustomization-dir>A diff exit status of 1 means differences; higher values are errors. Review the preview, then apply within the authorized scope.
kubectl diffmasks Secret data unless--show-secretsis passed, but ConfigMaps and rendered chart values are not masked; exclude sensitive values from captured output.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago Changed e4928113188f
- 11d ago Changed 07f59e0c81bc
- 12d ago Changed · -5 lines · -1 tokens per session cb20ef82aaf6
- 14d ago Changed 89dd41797822
- 20d ago Changed · -1 lines a5ce4d295eb3
- 23d ago Changed · -3 lines 631b156d2315
- 26d ago Changed · -2 lines 1ad93009b803
- 28d ago Changed 1ef66b49c672
- 29d ago First seen · 84 lines · 23 tokens per session scan A a86482b56381
kubernetes is a skill published in the GitHub repository fmind/dot (11 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 927 once invoked, about $0.0001 per session on Opus 5.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-09-17.
Other skills, from other repositories
cloud-run
Deploy container services to Google Cloud Run with Artifact Registry, keyless CI identity, Secret Manager, ko, or Dockerfiles.
k8s-local
Create and manage local Kubernetes clusters (k3d or kind) and deploy to them with kubectl, helm, helmfile, and skaffold. Use for local k8s cluster setup, dev loops, and debugging.
security-scan
Scan repositories with Trivy and gitleaks for vulnerabilities, IaC, secrets, licenses, images, and git history; triage concrete findings.
containerize
Build minimal, non-root OCI images — ko for Go or a distroless multi-stage Dockerfile — then scan, sign, and SBOM them. Use when containerizing or packaging an app for deployment.
google-cloud-operations
Operate Google Cloud with gcloud: pin account, configuration, project, and billing context for IAM, APIs, logs, and audits outside deployment.
terraform-stack
Canonical infrastructure-as-code stack — OpenTofu-first with tflint, trivy config scans, terraform-docs, native tests, and GCS state. Use for any Terraform or OpenTofu work.