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 NickCrew/Claude-Cortex --skill helm-chart-patternsgit clone --depth 1 https://github.com/NickCrew/Claude-CortexWrote 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/nickcrew/claude-cortex/helm-chart-patterns)<a href="https://agentmods.dev/skills/nickcrew/claude-cortex/helm-chart-patterns"><img src="https://agentmods.dev/badge/skills/nickcrew/claude-cortex/helm-chart-patterns.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.00037 | $0.01021 |
| Opus 5 | $0.00018 | $0.00511 |
| Sonnet 5 | $0.00007 | $0.00204 |
| Haiku 4.5 | $0.00004 | $0.00102 |
Grade A, and why
helm-chart-patterns 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- helm-chart-patterns — 94% identical, 18 lines differ
How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Helm Chart Patterns
Expert guidance for developing production-grade Helm charts covering chart structure, templating patterns, multi-environment configuration, dependency management, testing strategies, and distribution workflows for Kubernetes application packaging.
When to Use This Skill
- Creating reusable Helm charts for applications and services
- Building application catalogs and chart repositories
- Managing multi-environment deployments (dev, staging, production)
- Implementing advanced templating with conditionals and loops
- Managing chart dependencies and subcharts
- Implementing chart hooks for lifecycle management
- Testing and validating chart templates
- Packaging and distributing charts via repositories
- Using Helmfile for multi-chart orchestration
Core Concepts
Chart Types
- Application charts: Standard deployable charts for your services
- Library charts: Reusable template helpers (not directly installable)
Key Files
| File | Purpose |
|---|---|
Chart.yaml |
Metadata, version, dependencies |
values.yaml |
Default configuration |
values.schema.json |
Input validation |
templates/_helpers.tpl |
Reusable template functions |
templates/*.yaml |
Kubernetes manifests |
Template Essentials
- Quote strings:
{{ .Values.name | quote }} - Indent properly:
{{- toYaml . | nindent 4 }} - Use helpers:
{{ include "my-app.fullname" . }} - Check nil:
{{- if .Values.optional }}
Quick Reference
| Task | Load reference |
|---|---|
| Chart structure & Chart.yaml | skills/helm-chart-patterns/references/chart-structure.md |
| Values file patterns | skills/helm-chart-patterns/references/values-patterns.md |
| Template patterns & functions | skills/helm-chart-patterns/references/template-patterns.md |
| Dependencies & subcharts | skills/helm-chart-patterns/references/dependencies.md |
| Hooks & lifecycle | skills/helm-chart-patterns/references/hooks.md |
| Testing patterns | skills/helm-chart-patterns/references/testing.md |
| Packaging & distribution | skills/helm-chart-patterns/references/packaging.md |
| Helmfile multi-chart | skills/helm-chart-patterns/references/helmfile.md |
| Best practices checklist | skills/helm-chart-patterns/references/best-practices.md |
What ships with it
9 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.
- 4d ago First seen · 123 lines · 37 tokens per session scan A dbc6206c61f6
helm-chart-patterns is a skill published in the GitHub repository NickCrew/Claude-Cortex (38 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 1,021 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-09-03.
Other skills, from other repositories
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
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.
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.
kubernetes-skill
Prevent Kubernetes hallucinations by diagnosing and fixing failure modes: insecure workload defaults, resource starvation, network exposure, privilege sprawl, fragile rollouts, and API drift. Use when generating, reviewing, refactoring, or migrating manifests, Helm charts, Kustomize overlays, cluster policies, and…
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.
obol-stack
Monitor the Kubernetes cluster running the Obol Stack. Use when asked about pod status, logs, services, events, deployments, or diagnosing issues. Read-only access to own namespace via ServiceAccount.