Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/atretyak1985/swarmerynpx agentmods add skills/atretyak1985/swarmery/helm-chart-expertWrote 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/atretyak1985/swarmery/helm-chart-expert)<a href="https://agentmods.dev/skills/atretyak1985/swarmery/helm-chart-expert"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/helm-chart-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/atretyak1985/swarmery/helm-chart-expert"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/helm-chart-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.00078 | $0.03588 |
| Opus 5.5 | $0.00031 | $0.01435 |
| Sonnet 5.5 | $0.00016 | $0.00718 |
| Haiku 4.5 | $0.00008 | $0.00359 |
Grade A, and why
helm-chart-expert 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.
How it starts
The opening of the file, as written. The whole thing — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Author and validate Helm charts for the project's infrastructure and chart repos (project.json → repos). This skill covers chart structure, Go template patterns, values management, subchart dependencies, and validation workflows (lint, template render, dry-run). It does not cover end-to-end deploy orchestration (use deployment), Keycloak realm/client configuration (use keycloak), IaC drift detection (use infrastructure-as-code), or Docker image builds (use docker-build).
When to use this skill (triggers)
- Creating or modifying Helm chart templates (deployment, service, ingress, networkpolicy, etc.)
- Structuring or reviewing
values.yaml/values.<env>.yamlfiles - Managing subchart dependencies in
Chart.yamlandChart.lock - Running chart validation:
helm lint,helm template,helm upgrade --dry-run - Debugging template rendering errors (nil pointer, label mismatch, values not applied)
- Bumping chart versions and synchronizing umbrella/subchart versions
- Reviewing Helm template correctness with file:line citations
When NOT to use this skill (anti-triggers)
- End-to-end deploy orchestration (helm upgrade to a live cluster) -- use
deployment - Keycloak realm setup, client config, or Auth.js integration -- use
keycloak - Terraform drift detection or post-incident IaC capture -- use
infrastructure-as-code - Docker image builds or multi-arch buildx -- use
docker-build - Migration safety checks or schema alignment -- use
migration-check - GCP firewall rules or VM-level k8s debugging -- use
kubernetes-deployment - CI/CD pipeline YAML review -- use
gitlab-ci-cd
Required environment (Runtime: .claude/skills/helm-chart-expert/SKILL.md)
- Tools/libraries:
helm(v3.10+),kubectl(v1.28+),bash - Repos: the project's infrastructure and chart repos (project.json → repos)
- Validation script:
.claude/skills/helm-chart-expert/scripts/validate-chart.sh
Inputs
chart_path: string-- path to the chart directory (e.g.,<infra-repo>/)values_file: string(optional) -- path to the values file to validate againstoperation: enum-- one of:author,validate,review,debug
What ships with it
1 file 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 · 295 lines · 78 tokens per session scan A 3e763a11bb5a
helm-chart-expert is a skill published in the GitHub repository atretyak1985/swarmery (7 stars, last pushed today), licensed Apache-2.0. It adds 78 tokens to every session and 3,588 once invoked, about $0.0003 per session on Opus 5.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
commit-message
Use ANY time the user signals they want to commit staged changes — including bare "commit", "/commit", "commit this", "commit these changes", "let's commit", "make a commit", "git commit", "write a commit message", "make a conventional commit", "use conventional commits", or any equivalent phrasing in context (e.g.…
dependency-versions
MUST consult this skill before answering whenever the user's task involves external versioned dependencies — even if you think you can handle it directly. This applies to: checking if packages/tools are up to date, upgrading npm/pip/cargo/go dependencies, planning or writing CI/CD workflows (GitHub Actions, CircleCI…
finish
Ship phase — merge, PR, keep, or discard with pre-merge verification.
gws-quick-ref
Quick reference for gws CLI syntax — core patterns, key flags, pagination, field masks, and output formats.
excalidraw
Create or extend editable Excalidraw diagrams from descriptions or repository evidence using a local skeleton-to-scene converter.
style-ops
Maintain, validate or report on the Fakoli principles ledger, checking evidence pointers and keeping its Markdown projection synchronized.