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/dotfiles/k8s-localnpx skills add fmind/dotfiles --skill k8s-localgit clone --depth 1 https://github.com/fmind/dotfilesWrote 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/dotfiles/k8s-local)<a href="https://agentmods.dev/skills/fmind/dotfiles/k8s-local"><img src="https://agentmods.dev/badge/skills/fmind/dotfiles/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.00050 | $0.02339 |
| Opus 5 | $0.00025 | $0.01170 |
| Sonnet 5 | $0.00010 | $0.00468 |
| Haiku 4.5 | $0.00005 | $0.00234 |
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 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Local Kubernetes Cluster Management
Bootstrap and manage lightweight local Kubernetes clusters with k3d (default, Docker-based K3s) or kind, plus the local dev-tool ecosystem (kubectl, helm, helmfile, skaffold, k9s).
Global vs Project-Scoped Setup
When designing project local environments, choose the appropriate isolation scope:
- Project-Scoped Setup (Recommended for important/complex projects): Important projects must remain independent, self-contained, and reproducible across hosts. Do not rely on the global
k3d-localcluster or default configs. Instead, declare all dependencies (likek3d,kubectl,helm,flux2) under the[tools]section of the project's mise.toml, store cluster engine configurations within the repository, and isolate active workloads by generating temporary, process-scopedKUBECONFIGvariables. Author a project-scoped skill at.agents/skills/local-cluster/SKILL.mdto guide agents to use your local task vocabulary instead of globaldot clustercommands. - Global Setup (Optional fallback for small/simple projects): Simple projects or quick experiments without custom orchestration needs can rely on the global cluster configuration managed here. Use the unified
dot clusterCLI or manually bootstrap using the global templates.
Templates & Resources
- k3d Configuration: Deployed at
~/.config/k3d/local.yaml(source:dot_config/k3d/local.yaml). - kind Configuration: kind-config.yaml
- Local Cluster CLI: Deployed at
~/.local/bin/dot(source:dot/). - Ingress Template: ingress-template.yaml
Core Principles
- Cloud Agnostic: Local clusters must mirror production API interfaces. Avoid vendor-specific or platform-specific configurations unless mapping local routes.
- Engine Choice (Hybrid Pattern): Match the engine to the workflow. Use
k3dfor interactive developer loops (fast startup, built-in Traefik ingress, and registry integration). Usekindfor automated/disposable integration tests to validate vanilla, upstream-conformant Kubernetes API and security compliance. - Local Registry Dev Loop: Push locally built Docker images to the local registry at
registry.localhost:5050or load them directly into the cluster engine nodes. In-cluster pulls resolve that reference through the k3s containerd mirror, but a host-sidedocker pushto the same name is rejected as insecure until the daemon is configured — see the Registry Push Name gotcha. - Declarative Operations: Manage all workloads using declarative configurations (Helm, Helmfile, Skaffold, Kustomize) rather than raw imperatives.
What ships with it
2 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.
- 3d ago First seen · 149 lines · 50 tokens per session scan A 2574e628dcdf
k8s-local is a skill published in the GitHub repository fmind/dotfiles (4 stars, last pushed 4d ago), licensed MIT. It adds 50 tokens to every session and 2,339 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 skills, from other repositories
dotfiles-bootstrap
Bootstrap a workstation with the dotfiles framework. Takes a GitHub user / owner+repo / explicit clone URL and runs dot init (which shells out to chezmoi) with the right safety prompts. Honors the active agent profile (ask / plan / apply / audit) so it defaults to dry-run in safer modes and full apply in apply.
vibe
Delegate a coding task to a cheap AI model (Mistral Vibe by default, but any provider Vibe knows about — DeepSeek, Gemini Flash, etc.) and supervise the result via git diff. Claude orchestrates, the cheap model codes. Claude consumes 500-1500 tokens per delegation regardless of how many file reads the delegate does…
aiq-research
Use when asked to run deep research or AI-Q research through a reachable NVIDIA AI-Q Blueprint backend.
obsidian-bases
Obsidian Bases database feature for YAML-based interactive note views. Use when creating .base files, writing filter queries, building formulas, configuring table/card views, or working with Obsidian properties and frontmatter databases.
telegram
Send notifications, interactive questions, or multiple-choice polls to the user via Telegram. Use when the user asks to be notified ("ping me", "notify me on Telegram", "ask me when..."), when a long-running task finishes and the user is likely away, when an irreversible action needs out-of-band confirmation, or when…
chezmoi-expert
Comprehensive chezmoi dotfiles management expertise including templates, cross-platform configuration, file naming conventions, and troubleshooting. Covers source directory management, reproducible environment setup, and chezmoi templating with Go templates. Use when user mentions chezmoi, dotfiles, cross-platform…