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 skills add Aidas-dev/k8s-agent-skills --skill helm-opsgit 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-ops)<a href="https://agentmods.dev/skills/aidas-dev/k8s-agent-skills/helm-ops"><img src="https://agentmods.dev/badge/skills/aidas-dev/k8s-agent-skills/helm-ops.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.00058 | $0.02146 |
| Opus 5 | $0.00029 | $0.01073 |
| Sonnet 5 | $0.00012 | $0.00429 |
| Haiku 4.5 | $0.00006 | $0.00215 |
Grade A, and why
helm-ops 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 7d 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 — 260 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Helm — Operations
For chart writing (templates, values, testing) see helm-chart.
⚠️ Production Reminder
helm install / helm upgrade is for dev, debug, and emergency only. Day-2 operations go through GitOps:
| Tool | Resource |
|---|---|
| Flux | HelmRelease (helm.toolkit.fluxcd.io/v2) |
| ArgoCD | Application with Helm source |
See GitOps Integration below.
Release Inspection & Troubleshooting
# List releases
helm list -n production # namespace
helm list -A # all namespaces
helm list -n production -a # include failed/uninstalled
helm list -n production --filter "myapp" # filter by name
helm list -n production --date --reverse # newest first
# Inspect release state
helm status myapp -n production # resources + notes
helm history myapp -n production # revision history
helm get values myapp -n production # current values
helm get values myapp -n production --revision 2 # specific revision
helm get manifest myapp -n production # rendered K8s manifests
helm get manifest myapp -n production --revision 2
helm get notes myapp -n production # install-time output
helm get hooks myapp -n production # hooks in release
helm get all myapp -n production # everything
# Compare revisions
diff <(helm get manifest myapp -n production --revision 2) \
<(helm get manifest myapp -n production --revision 3)
# Dry-run / debug
helm install myapp ./mychart --dry-run -f values-prod.yaml
helm upgrade myapp ./mychart --dry-run --server-side -f values-prod.yaml # Helm 4 SSA
helm template myapp ./mychart -f values.yaml > rendered.yaml # no cluster
helm template myapp ./mychart --show-only templates/deployment.yaml
helm install myapp ./mychart --debug -f values.yaml # full template debug output
# Inspect remote charts
helm show chart oci://ghcr.io/myorg/mychart --version 0.1.0
helm show values oci://ghcr.io/myorg/mychart --version 0.1.0
helm show readme oci://ghcr.io/myorg/mychart --version 0.1.0
helm show crds oci://ghcr.io/myorg/mychart --version 0.1.0
# Troubleshoot failed release
helm status myapp -n production # what's the status
helm history myapp -n production # find last good revision
helm get values myapp -n production --revision 5 # what values caused it
helm get manifest myapp -n production --revision 5 # what rendered
helm rollback myapp 4 -n production --cleanup-on-fail
helm lint ./mychart -f values-prod.yaml # local validation
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.
- 7d ago First seen · 260 lines · 58 tokens per session scan A 9066b2372211
helm-ops is a skill published in the GitHub repository Aidas-dev/k8s-agent-skills (2 stars, last pushed 24d ago), licensed MIT. It adds 58 tokens to every session and 2,146 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
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.