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/bergerx/kubectl-status/generate-templatenpx skills add bergerx/kubectl-status --skill generate-templategit clone --depth 1 https://github.com/bergerx/kubectl-statusWrote 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/bergerx/kubectl-status/generate-template)<a href="https://agentmods.dev/skills/bergerx/kubectl-status/generate-template"><img src="https://agentmods.dev/badge/skills/bergerx/kubectl-status/generate-template.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.00030 | $0.00993 |
| Opus 5 | $0.00015 | $0.00496 |
| Sonnet 5 | $0.00006 | $0.00199 |
| Haiku 4.5 | $0.00003 | $0.00099 |
Grade A, and why
generate-template 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 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.
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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kubectl-status Template Generator
Generate kubectl-status Go template files for resource kinds and write them to
~/.kubectl-status/templates/<Kind>.tmpl.
Reference material — read before writing
CONVENTIONS.md— output philosophy, color rules, and all template design conventions. Read this first.pkg/plugin/templates/common.tmpl— all shared sub-templates and available functions.pkg/plugin/templates/— built-in templates as style examples.~/.kubectl-status/templates/— user CRD template examples.
Steps
1. Identify the resource
kubectl api-resources | grep -i <name>
Note the exact Kind string (case-sensitive — used as the template define name) and the APIVERSION column value.
2. Read the full CRD schema
kubectl get crd <full-crd-name> -o json | jq '.spec.versions[0].schema.openAPIV3Schema.properties'
Read spec and status sub-schemas in full — not just top-level keys. For each field, check its description to understand what it means. Use that meaning to decide whether it warrants inclusion, applying the output philosophy in CONVENTIONS.md.
Pay specific attention to:
- Timestamps — apply the date formatting rules in CONVENTIONS.md § Dates.
- Booleans and enums — never emit raw
true/false; emit a meaningful label only when the value is operationally interesting. requiredlists — note them, but do not treat them as a render-time guarantee. Third-party CRD schemas are looser than their docs, they change between operator versions, and--local/-frenders manifests that never passed API-server validation. See CONVENTIONS.md § Never trust a field to be present — a nil reaching a color function aborts the render of the whole object.
3. Sample live instances
kubectl get <resource> -A --no-headers | head -5
kubectl get <resource> <name> -n <ns> -o json
Cross-reference the schema against what is actually populated. Skip status fields that are never set and spec fields always at their default.
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 · 87 lines · 30 tokens per session scan A aeda0b405dc2
generate-template is a skill published in the GitHub repository bergerx/kubectl-status (122 stars, last pushed yesterday), licensed Apache-2.0. It adds 30 tokens to every session and 993 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-08-30.
Other skills, from other repositories
timoni
Use when deploying applications to Kubernetes with Timoni. Covers installing and upgrading module instances from OCI registries, composing multi-app deployments with bundles, injecting values from clusters or CI with runtimes, targeting multiple clusters, and authoring, testing, signing and publishing modules with CUE.
startup-chain-change
Modifies the local startup chain including image build, container serve/bootstrap logic, and canonical smoke test behavior. Use when changing vllm-sr serve behavior, image selection or pull policy, container startup sequences, local Docker/Make bootstrap, or canonical smoke config.
implementing-opa-gatekeeper-for-policy-enforcement
Enforce Kubernetes admission policies using OPA Gatekeeper with ConstraintTemplates, Rego rules, and the Gatekeeper policy library.
detecting-container-drift-at-runtime
Detect unauthorized modifications to running containers by monitoring for binary execution drift, file system changes, and configuration deviations from the original container image.
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
implementing-kubernetes-network-policy-with-calico
Implement Kubernetes network segmentation using Calico NetworkPolicy and GlobalNetworkPolicy for zero-trust pod-to-pod communication.