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 skills/fmind/dot/k8s-localnpx skills add fmind/dot --skill k8s-localgit 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/k8s-local)<a href="https://agentmods.dev/skills/fmind/dot/k8s-local"><img src="https://agentmods.dev/badge/skills/fmind/dot/k8s-local.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.00044 | $0.01227 |
| Opus 5 | $0.00022 | $0.00613 |
| Sonnet 5 | $0.00009 | $0.00245 |
| Haiku 4.5 | $0.00004 | $0.00123 |
Grade A, and why
k8s-local 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 yesterday.
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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Local Kubernetes
Run an opt-in k3d (default) or kind cluster on the workstation and deploy into it declaratively. cloud-run is the default deploy target, so the Kubernetes tools are commented out in the global mise config: uncomment them or pin them in the project mise.toml first.
Workflow
-
Choose the scope: quick experiments use the global
dot clusterfrom dot-cli; a real project stays self-contained (see the project-scope gotcha). -
Check Docker: run
docker infobefore starting, stopping, or configuring a cluster. -
Start the cluster, OFF by Default: run it only for a short verification window and stop it as soon as the task ends; k3d containers use
restart=unless-stopped, so they return after a reboot until stopped.dot cluster start # k3d from ~/.config/k3d/local.yaml: idempotent, owner-only kubeconfig, never touches the default context kind create cluster --config ~/.agents/skills/k8s-local/references/kind-config.yaml -
Target the isolated context: never switch the default kubeconfig; a renamed context needs
dot cluster --context <name> <command>.kubectl --kubeconfig ~/.kube/dot/local.yaml --context k3d-local get nodes dot cluster namespace <namespace> -
Validate manifests:
kubeconform -strict <path>for schema,kube-linter lint <path>for practices and security. -
Publish images: push to the local registry or sideload, always with a specific tag and
imagePullPolicy: IfNotPresentorNeverin the manifest.docker tag <image>:<tag> registry.localhost:5050/<image>:<tag> && docker push registry.localhost:5050/<image>:<tag> k3d image load <image>:<tag> -c local # k3d sideload kind load docker-image <image>:<tag> --name local-cluster # kind sideload -
Deploy declaratively:
helm upgrade --install <release> <chart> -n <namespace> --create-namespace,helmfile apply,skaffold dev, orkubectl apply -k <dir>; expose with ingress-template.yaml. -
Diagnose with bounded evidence:
dot cluster diagnose --namespace <namespace>verifies the isolated target, runs only the read-only allowlist, redacts secrets, and writes an owner-only manifest; review it locally before sharing. -
Stop or delete:
dot cluster stopis the resting state;dot cluster deleteis destructive and asks for confirmation;kind delete cluster --name local-clusterremoves the kind cluster.
What ships with it
3 files 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.
- yesterday First seen · 60 lines · 44 tokens per session scan A b70e98a74361
k8s-local is a skill published in the GitHub repository fmind/dot (4 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 1,227 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-09-03.
Other skills, from other repositories
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.
cloud-run
Deploy container services to Google Cloud Run with Artifact Registry, keyless CI identity, Secret Manager, ko, or Dockerfiles.
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.
dot-cli
Use the dot CLI (fmind/dotfiles) to verify the environment, pull repos, manage the local k3d cluster, log agent sessions, and prune caches. Use when running or scripting any dot command.
go-stack
Build Go projects, libraries, CLIs, TUIs, web apps, or ADK agents with the standard package layout and pinned tooling.