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 Awish021/opencode --skill helm-expertgit clone --depth 1 https://github.com/Awish021/opencodeWrote 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/awish021/opencode/helm-expert)<a href="https://agentmods.dev/skills/awish021/opencode/helm-expert"><img src="https://agentmods.dev/badge/skills/awish021/opencode/helm-expert/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.
<a href="https://agentmods.dev/skills/awish021/opencode/helm-expert"><img src="https://agentmods.dev/badge/skills/awish021/opencode/helm-expert.svg" alt="Reviewed on agentmods" width="80" 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.00921 |
| Opus 5.5 | $0.00015 | $0.00368 |
| Sonnet 5.5 | $0.00007 | $0.00184 |
| Haiku 4.5 | $0.00004 | $0.00092 |
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 1mo 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.
This is a copy
94% identical to helm-chart-patterns — 18 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 105 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.
- 1mo ago First seen · 105 lines · 37 tokens per session scan A 615c57d8252d
helm-chart-patterns is a skill published in the GitHub repository Awish021/opencode (11 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 921 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to helm-chart-patterns, differing in 18 lines, and is treated as a copy.
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…
bdd-container-update
Update the BDD test container image when its dependencies or runtime change. Determines version bump (major vs minor vs patch), rebuilds the Docker image, pushes to GitLab registry, and updates the image tag in starttest.sh. Test source (tests/, features/, scripts/, data/, conftest.py) is bind-mounted from the host…
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.
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.
polar-local-environment
This skill should be used when setting up or managing Polar local development environment with Docker.