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/cookiemonsterdev/agents-skills/helm-docsnpx skills add cookieMonsterDev/agents-skills --skill helm-docsgit clone --depth 1 https://github.com/cookieMonsterDev/agents-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/cookiemonsterdev/agents-skills/helm-docs)<a href="https://agentmods.dev/skills/cookiemonsterdev/agents-skills/helm-docs"><img src="https://agentmods.dev/badge/skills/cookiemonsterdev/agents-skills/helm-docs.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.00081 | $0.01071 |
| Opus 5 | $0.00041 | $0.00535 |
| Sonnet 5 | $0.00016 | $0.00214 |
| Haiku 4.5 | $0.00008 | $0.00107 |
Grade A, and why
helm-docs 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 3d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Helm questions are easy to answer from stale memory or Helm 3 assumptions that no longer apply in Helm 4. Use this skill to ground answers in the official Helm documentation and return the closest authoritative page instead of generic Kubernetes packaging advice.
When to Use
Use this skill when the request is about:
- Helm concepts: charts, releases, repositories, and values
- Installing, upgrading, rolling back, and uninstalling Helm releases
- Searching charts on Artifact Hub or configured repositories
- Chart development, templating, linting, and packaging
- Values files,
--set,--set-json, and override precedence - Helm plugins and the Go SDK
- Helm 4 overview, breaking changes, and migration from Helm 3
- Helm CLI command reference and flags
Do not use this skill for:
- Core Kubernetes API resources, kubectl, or cluster administration without Helm context. Use
kubernetes-docsinstead. - Raw Docker image builds or Compose files. Use
docker-docsinstead. - Terraform Helm provider configuration unless the question is specifically about Helm chart behavior documented on helm.sh.
- Argo CD, Flux, or other GitOps tools unless the question is about Helm chart mechanics documented by Helm.
Workflow
1. Classify the request
Decide which bucket the question belongs to before searching:
- Introduction and core concepts
- Installing and using Helm day to day
- Chart development and templating
- Best practices and chart design
- Plugins and extensibility
- Helm CLI command reference
- Helm 4 migration and version differences
If you need a quick starting point, load references/topic-map.md and jump to the closest section.
2. Search official Helm docs first
- Treat
helm.sh/docsas the source of truth for Helm. - Prefer pages under https://helm.sh/docs/.
- Default to the current documentation version (4.2.4) unless the user specifies another supported version.
- Search with the user's exact terms plus focused Helm phrases such as
helm upgrade,values.yaml,chart hooks,helm template,OCI, orArtifact Hub. - When multiple pages are plausible, compare 2-3 candidate pages and pick the one that most directly answers the user's question.
- For Helm 4 questions, check the Helm 4 Overview before answering from Helm 3 knowledge.
What ships with it
2 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.
- 3d ago First seen · 101 lines · 81 tokens per session scan A ced52572acf0
helm-docs is a skill published in the GitHub repository cookieMonsterDev/agents-skills (4 stars, last pushed 14d ago), licensed MIT. It adds 81 tokens to every session and 1,071 once invoked, about $0.0004 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
wrangler
Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over…
managing-astro-local-env
Manage local Airflow environment with Astro CLI (Docker and standalone modes). Use when the user wants to start, stop, or restart Airflow, view logs, query the Airflow API, troubleshoot, or fix environment issues. For project setup, see setting-up-astro-project.
aws-cloudformation-ecs
Provides AWS CloudFormation patterns for ECS clusters, task definitions, services, container definitions, auto scaling, blue/green deployments, CodeDeploy integration, ALB integration, service discovery, monitoring, logging, template structure, parameters, outputs, and cross-stack references. Use when creating ECS…
pentest-cloud-infrastructure
Cloud security posture management and container security assessment for AWS, Azure, GCP, and Kubernetes.
datarobot-workload-api
Use when the user wants to create, configure, scale, debug, observe, or roll out container workloads on DataRobot's Workload API. Triggers include: deploying a container as a managed service, listing/starting/stopping workloads, changing replica counts or autoscaling, picking CPU/GPU compute bundles, injecting…
kubernetes-operations
Covers running workloads through Kubernetes's control loop — requests/limits, liveness/readiness/startup probes, reading describe/events to debug CrashLoopBackOff, OOMKilled, Pending, or empty endpoints, safe rollouts and undo, and guardrails like PodDisruptionBudgets. Use this whenever the user is debugging a pod…