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/orka-agents/orka/kindctlnpx skills add orka-agents/orka --skill kindctlgit clone --depth 1 https://github.com/orka-agents/orkaWrote 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/orka-agents/orka/kindctl)<a href="https://agentmods.dev/skills/orka-agents/orka/kindctl"><img src="https://agentmods.dev/badge/skills/orka-agents/orka/kindctl.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.1 | $0.00055 | $0.01169 |
| Opus 5 | $0.00028 | $0.00584 |
| Sonnet 5 | $0.00011 | $0.00234 |
| Haiku 4.5 | $0.00006 | $0.00117 |
Grade C, and why
kindctl scanned grade C with 1 finding 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 6d 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
- `~/.kube/config` is a shared mutable global and must not be used for kindctl-managed clusters. How it starts
The opening of the file, as written. The whole thing — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kindctl
Use this skill whenever work involves a local kind cluster, local k8s/Kubernetes, Kubernetes-in-Docker, or repo/worktree-specific test clusters.
Mental model
kindclusters are global to the Docker daemon.~/.kube/configis a shared mutable global and must not be used for kindctl-managed clusters.kindctlderives a cluster name from the current repo/worktree path and stores its kubeconfig in~/.kube/kind/<name>.kubeconfig.- The current directory is enough: random repos and git worktrees do not need to know anything special.
Golden rule for agents
Never run bare kubectl or helm against a kindctl-managed cluster.
Prefer:
.agents/skills/kindctl/bin/kindctl kubectl get nodes
.agents/skills/kindctl/bin/kindctl exec -- helm list
Do not run:
kubectl get pods
kubectl config use-context kind-something
kind create cluster
Installation
This skill is vendored into the repo at .agents/skills/kindctl/. If another
harness needs to expose it, create an external skills/kindctl symlink that points
back to this canonical directory; this repo does not keep .codex or .copilot
mirrors. Invoke the wrapper by its repo-relative path:
.agents/skills/kindctl/bin/kindctl <command>
The skill itself should invoke bin/kindctl by absolute path or by resolving the skill directory. Do not rely on shell aliases.
Commands
kindctl create [--config F] [--tag T] [--k8s-version vX.Y.Z]
kindctl delete [--tag T]
kindctl kubectl [--tag T] <args...>
kindctl exec [--tag T] -- <cmd...>
kindctl path [--tag T]
kindctl ctx [--tag T]
kindctl env [--tag T]
kindctl load [--tag T] <image>
kindctl hibernate [--tag T]
kindctl resume [--tag T]
kindctl list [--workspace|--all]
kindctl doctor
kindctl prune --workspace [--yes]
kindctl prune --dead [--yes]
kindctl nuke [--yes]
If kindctl is not on PATH, use the repo-relative path:
.agents/skills/kindctl/bin/kindctl <command>
Recipes
Create and use a repo cluster
What ships with it
4 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.
- 6d ago First seen · 176 lines · 55 tokens per session scan C 2a726ad9e797
kindctl is a skill published in the GitHub repository orka-agents/orka (22 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 1,169 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
vigilante-issue-implementation-on-kubernetes
Implement a GitHub issue end-to-end when Vigilante dispatches work for a Kubernetes-focused repository with manifest hardening and workload security guidance.
docker-compose-launch
Launch worktree-scoped local services for issue implementation when a monorepo skill requires database dependencies.
container-apps-deployment
Container Apps deployment gotchas and SPA frontend patterns for Azure. Supplements the official azure-prepare plugin skill with additional patterns for zone redundancy, azure.yaml configuration, and SPA frontend deployment (VITEAPIURL). USE FOR: Container Apps zone redundancy errors, managed-identity ACR pulls…
vigilante-issue-implementation-on-docker
Implement a GitHub issue end-to-end when Vigilante dispatches work for a Docker-focused repository with Dockerfile best practices, image hardening, and secret-safe build guidance.
kubernetes-basics
Core Kubernetes concepts including pods, deployments, services, and common troubleshooting patterns.
deployment
CI/CD pipeline verification, Docker container security, environment management, and deployment workflow.