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/greedychipmunk/agent-skills/helmnpx skills add greedychipmunk/agent-skills --skill helmgit clone --depth 1 https://github.com/greedychipmunk/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/greedychipmunk/agent-skills/helm)<a href="https://agentmods.dev/skills/greedychipmunk/agent-skills/helm"><img src="https://agentmods.dev/badge/skills/greedychipmunk/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 | $0.00038 | $0.00922 |
| Opus 5 | $0.00019 | $0.00461 |
| Sonnet 5 | $0.00008 | $0.00184 |
| Haiku 4.5 | $0.00004 | $0.00092 |
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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
helm
Use this skill to keep Helm-based Kubernetes deployments reproducible, auditable, and safe across environments.
Intent Router
| Request | Reference | Load When |
|---|---|---|
| Install Helm, add repos, configure registries | resources/install-and-setup.md |
User needs to install Helm or configure repositories |
| install/upgrade/list/rollback/template commands | resources/command-cookbook.md |
User needs day-to-day Helm release operations |
| Chart.yaml, templates, values, helpers | resources/chart-authoring.md |
User wants to author or modify a Helm chart |
| Release lifecycle, --atomic, --wait, diff plugin | resources/release-management.md |
User asks about release management or upgrade strategies |
Quick Start
# Add a chart repository
helm repo add bitnami https://charts.bitnami.com/bitnami
helm repo update
# Search for a chart
helm search repo bitnami/nginx
# Inspect default values
helm show values bitnami/nginx
# Install with custom values
helm install my-nginx bitnami/nginx --set service.type=ClusterIP -n my-namespace
# Upgrade with a values file
helm upgrade my-nginx bitnami/nginx -f values.yaml -n my-namespace
# List releases
helm list -A
Core Command Tracks
- Install:
helm install <release> <chart> [flags]— create a new release - Upgrade:
helm upgrade --install <release> <chart>— create or update release - Rollback:
helm rollback <release> [revision]— revert to previous revision - Template:
helm template <release> <chart>— render manifests locally without applying - Values:
helm get values <release>— inspect values used by a deployed release - Status:
helm status <release>— show release info and notes - Uninstall:
helm uninstall <release>— remove release and resources
Safety Guardrails
- Always run
helm upgrade --dry-run --debugorhelm templatebefore applying changes to production. - Use the helm diff plugin (
helm diff upgrade) to inspect what will change before applying. - Use
--atomicin CI pipelines so failed upgrades automatically roll back. - Never pass secrets via
--set; use a secrets manager or the helm-secrets plugin. - Always specify
--namespaceexplicitly; do not rely on the default namespace. - Pin chart versions with
--versionin production to ensure reproducibility. - Confirm before running
helm uninstall; it removes all resources managed by the release.
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.
- 5d ago First seen · 96 lines · 38 tokens per session scan A 8937619b6ea5
helm is a skill published in the GitHub repository greedychipmunk/agent-skills (17 stars, last pushed 12d ago), licensed MIT. It adds 38 tokens to every session and 922 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
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.