A guide to Helm, a tool that packages Kubernetes application configuration into reusable charts and tracks installed releases. Kubernetes runs applications in containers across a cluster.

Use it to create charts, deploy the same application across environments, manage dependencies, render and lint templates, and recover from failed upgrades.

It reduces repeated configuration, makes environment-specific settings manageable, and provides a history for upgrades and rollbacks.

helm — Skill for Claude Code by alivirgo

Install

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.

Any agent

npx skills add alivirgo/Major-AI-Skills --skill helm

Clone the repo

git clone --depth 1 https://github.com/alivirgo/Major-AI-Skills

Made for: Claude Code.

Or install major-ai-skills, the plugin that ships this one along with the rest of its 147 skills, 7 plugins.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/alivirgo/major-ai-skills/helm/github.svg)](https://agentmods.dev/skills/alivirgo/major-ai-skills/helm)

Your own site

<a href="https://agentmods.dev/skills/alivirgo/major-ai-skills/helm"><img src="https://agentmods.dev/badge/skills/alivirgo/major-ai-skills/helm/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/alivirgo/major-ai-skills/helm"><img src="https://agentmods.dev/badge/skills/alivirgo/major-ai-skills/helm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 869 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00022	$0.00869
Opus 5	$0.00011	$0.00434
Sonnet 5	$0.00004	$0.00174
Haiku 4.5	$0.00002	$0.00087

Measured yesterday against content hash abaafa045aca, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

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 yesterday.

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.

skills/helm/SKILL.md · 118 lines

How it starts

The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Helm Chart Packaging AI Skill Guide

Overview & Engine Architecture

Helm packages Kubernetes manifests as charts: templates plus a values.yaml configuration surface. Releases track what was installed; upgrades render a new revision and apply the diff. Agents write maintainable templates, keep secrets out of committed values, and always render locally before touching a cluster.

Chart.yaml + values.yaml + templates/
            |
            v
    helm template / lint
            |
            v
    helm upgrade --install  ->  Kubernetes API
            |
            v
      release history (rollback)

When to use this skill

Packaging repeated Kubernetes YAML into a chart
Promoting the same chart across dev/stage/prod with value files
Debugging failed hooks or bad template rendering
Vendoring chart dependencies

Operational directives

Run helm lint and helm template before every install/upgrade.
Treat values.yaml as public defaults; inject secrets via --set-file, sealed secrets, or external secret stores.
Pin dependency chart versions in Chart.yaml / Chart.lock.
Prefer upgrade --install with an explicit --namespace and --create-namespace when intentional.
Keep templates readable: named helpers in _helpers.tpl, no copy-paste label blocks.

Chart layout

mychart/
  Chart.yaml
  values.yaml
  values.schema.json   # optional but valuable
  templates/
    _helpers.tpl
    deployment.yaml
    service.yaml
    ingress.yaml
  charts/              # vendored deps
  Chart.lock

Chart.yaml sketch:

apiVersion: v2
name: mychart
description: Example API chart
type: application
version: 0.3.0
appVersion: "1.4.2"
dependencies:
  - name: redis
    version: 19.0.0
    repository: https://charts.bitnami.com/bitnami
    condition: redis.enabled

Command loop

helm create mychart
helm dependency update ./mychart
helm lint ./mychart
helm template mychart ./mychart -f values.prod.yaml > /tmp/render.yaml
helm upgrade --install mychart ./mychart -n apps --create-namespace -f values.prod.yaml
helm history mychart -n apps
helm rollback mychart 2 -n apps

Read the full file on GitHub · 118 lines

Changes

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.

yesterday Changed · -4 tokens per session abaafa045aca
6d ago First seen · 118 lines · 26 tokens per session scan A 795a133f9e90

Subscribe to this mod's changes

helm is a skill published in the GitHub repository alivirgo/Major-AI-Skills (1 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 869 once invoked, about $0.0001 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-09-05.

Cloud Containers DevOps and cloud agent-skills agentic-skills ai-agent-skills ai-agents ai-coding charts claude helm kubernetes templating values

kubernetes-operator

Deploy and manage applications on Kubernetes. Covers deployments, services, ingress, HPA, secrets, and production-grade cluster configuration.

AtulPurohit/Antigravity-Awesome-Skills · 30 tokens

kubernetes

Kubernetes orchestration authority — pods, deployments, services, ingress, helm charts, kustomize overlays, RBAC, network policies, operators, StatefulSets for databases, production-grade cluster hardening, and kubectl workflows.

LuuOW/meridian-mcp · 48 tokens

nestjs-deployment

Containerize NestJS apps with multi-stage Docker builds, tune Node.js memory, and implement graceful shutdown hooks. Use when writing Dockerfiles, configuring K8s deployments, or adding shutdown hooks for NestJS.

FilippoDeSilva/skills · 46 tokens

nvca-values-customization

Customize NVCA Operator Helm chart values in the native monorepo. Use when modifying vendored defaults, changing stack-derived install values, adding deployment-time overrides, or updating scripts under deploy/helm/nvca-operator.

NVIDIA/nvcf · 51 tokens

nvca-self-managed-install

Install or validate the NVCA Operator chart against a self-managed NVCF control plane from the native monorepo. Use when the control plane comes from deploy/stacks/self-managed and NVCA must be installed with stack-derived image repository settings.

NVIDIA/nvcf · 55 tokens

helm-expert

Expert-level Helm 3 package management, chart development, templating, and production operations. Use when the user mentions Kubernetes, package manager, charts, templates, or deployment, or when the task involves Helm Architecture, Chart Structure, Values.yaml, or Helm Hooks.

personamanagmentlayer/pcl · 57 tokens