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 dallay/agents-skills --skill helm-chartsgit clone --depth 1 https://github.com/dallay/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/dallay/agents-skills/helm-charts)<a href="https://agentmods.dev/skills/dallay/agents-skills/helm-charts"><img src="https://agentmods.dev/badge/skills/dallay/agents-skills/helm-charts/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/dallay/agents-skills/helm-charts"><img src="https://agentmods.dev/badge/skills/dallay/agents-skills/helm-charts.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.00064 | $0.02906 |
| Opus 5 | $0.00032 | $0.01453 |
| Sonnet 5 | $0.00013 | $0.00581 |
| Haiku 4.5 | $0.00006 | $0.00291 |
Grade A, and why
helm-charts scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- name: curl-test How it starts
The opening of the file, as written. The whole thing — 371 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
- Creating a new Helm chart for a Kubernetes application.
- Writing or reviewing Helm templates (
templates/,_helpers.tpl). - Managing chart dependencies and multi-chart deployments.
- Configuring hooks for lifecycle events (migrations, backups, cleanup).
- Debugging template rendering issues or failed releases.
Critical Patterns
- Named Templates in
_helpers.tpl: ALWAYS extract reusable label sets, selectors, and name logic into named templates. Duplicating labels across resources is a maintenance trap. - Values Schema Validation: Provide a
values.schema.jsonto catch misconfiguration early, before templates render invalid YAML. - Immutable Selectors: NEVER change
matchLabelsselectors after initial deployment — Kubernetes rejects updates to immutable fields and the release breaks. - Quote All Strings in Templates: Use
{{ .Values.foo | quote }}for string values to prevent YAML type coercion ("true"becomes booleantruewithout quotes). - Resource Naming Conventions: Include release name in resource names via
{{ include "mychart.fullname" . }}to support multiple installations in the same namespace. - Hook Weight and Delete Policy: Always set
helm.sh/hook-weightfor ordering andhelm.sh/hook-delete-policyto clean up completed hook resources.
Code Examples
Chart Structure
mychart/
├── Chart.yaml # Chart metadata and dependencies
├── Chart.lock # Locked dependency versions (committed)
├── values.yaml # Default configuration values
├── values.schema.json # Optional: JSON Schema for values validation
├── templates/
│ ├── _helpers.tpl # Named template definitions
│ ├── deployment.yaml
│ ├── service.yaml
│ ├── ingress.yaml
│ ├── configmap.yaml
│ ├── secret.yaml
│ ├── hpa.yaml
│ ├── serviceaccount.yaml
│ └── tests/
│ └── test-connection.yaml
└── charts/ # Dependency charts (populated by helm dep update)
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.
- 9d ago First seen · 371 lines · 64 tokens per session scan A 518a84be6b5c
helm-charts is a skill published in the GitHub repository dallay/agents-skills (2 stars, last pushed 17d ago), licensed MIT. It adds 64 tokens to every session and 2,906 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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.