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/aidas-dev/k8s-agent-skills/helmnpx skills add Aidas-dev/k8s-agent-skills --skill helmgit clone --depth 1 https://github.com/Aidas-dev/k8s-agent-skillsWrote 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/aidas-dev/k8s-agent-skills/helm)<a href="https://agentmods.dev/skills/aidas-dev/k8s-agent-skills/helm"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/helm.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.00000 | $0.01158 |
| Opus 5 | $0.00000 | $0.00579 |
| Sonnet 5 | $0.00000 | $0.00232 |
| Haiku 4.5 | $0.00000 | $0.00116 |
Grade A, and why
helm 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 5d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Helm — Skill Router
Latest: v4.2.3 (v3.21.3 support until Nov 2026)
⚠️ Production Warning
Do not use helm install / helm upgrade manually or from CI for production. Manual Helm bypasses drift detection, audit trail, Git-as-truth, and rollback-via-revert.
| Use GitOps instead |
|---|
Flux: HelmRelease (helm.toolkit.fluxcd.io/v2) |
ArgoCD: Application with Helm source |
Helm CLI is for development, chart writing, debugging, and emergency recovery — not day-2 operations.
Which Sub-Skill?
Match the user's request against the trigger keywords below, then call skill(name="<matched-skill>") to load the sub-skill's full content.
Routing Table
| Trigger keywords | User wants to... | Skill to load |
|---|---|---|
| chart, template, HelmRelease values, _helpers.tpl, values.yaml, schema, write, create, modify, library chart, chart testing, helm unittest | Write or modify a Helm chart | helm-chart |
| install, upgrade, rollback, inspect, release, status, get values, get manifest, history, failed, troubleshoot, debug, OCI, push, pull, hook, GitOps, Flux, ArgoCD, HelmRelease, drift | Deploy, inspect, or troubleshoot releases | helm-ops |
Decision Tree
If routing is ambiguous:
- User is writing code (templates, YAML, values, helpers) →
helm-chart - User is running commands (install, inspect, debug, push) →
helm-ops - User is asking about both? → Load
helm-chartfirst (chart must exist before deploying), thenhelm-ops
When NOT to load this router
- User question is about a specific product's Helm chart (e.g. Higress, Vault, MariaDB) → load that product's
*-helmskill instead (e.g.higress-helm,vault-helm) - User needs Terraform for Helm releases → load
harbor-terraformor similar - User is working with ArgoCD or Flux generally (not Helm-specific) → load their respective skills
- User just needs a quick CLI reference → router's Quick CLI Reference section below is sufficient
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.
- 5d ago First seen · 93 lines · 0 tokens per session scan A 1419c73a7479
helm is a skill published in the GitHub repository Aidas-dev/k8s-agent-skills (2 stars, last pushed 22d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,158 tokens. 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
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.
securing-kubernetes-on-cloud
This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…
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-rbac-hardening-for-kubernetes
Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.
docker-socket-mount
Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.