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 gke-labs/kube-agents --skill gitops-helm-chartgit clone --depth 1 https://github.com/gke-labs/kube-agentsWrote 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/gke-labs/kube-agents/gitops-helm-chart)<a href="https://agentmods.dev/skills/gke-labs/kube-agents/gitops-helm-chart"><img src="https://agentmods.dev/badge/skills/gke-labs/kube-agents/gitops-helm-chart/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/gke-labs/kube-agents/gitops-helm-chart"><img src="https://agentmods.dev/badge/skills/gke-labs/kube-agents/gitops-helm-chart.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.00179 | $0.03375 |
| Opus 5.5 | $0.00072 | $0.01350 |
| Sonnet 5.5 | $0.00036 | $0.00675 |
| Haiku 4.5 | $0.00018 | $0.00337 |
Grade A, and why
gitops-helm-chart 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 today.
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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Third-Party Helm Charts Through GitOps
A chart reaches a cluster from this agent one way: as a declaration in the
GitOps repository that the customer's reconciler renders and applies after a
human merges it. This skill writes that declaration and opens the pull
request through submit-suggestion. It never runs helm. The shell
sandbox holds no cluster credential and has no route to a chart repository,
so helm install, helm upgrade, helm template and helm pull all fail
there, and asking for a token to hand to helm is refused by the credential
broker. Those refusals are the design, not obstacles to route around.
When to Use
- Install a chart on a cluster: "install cert-manager on prod-east", "add external-dns to the staging clusters".
- Upgrade or reconfigure a chart the repository already declares: a new version, a changed value.
- A packaged third-party component whose documented install is a Helm chart, even when the user did not say "Helm".
When NOT to Use
- kube-agents itself: an operator installs and upgrades it with the
installer (
upgrade.sh), which this agent does not run. - Plain Kubernetes YAML you write yourself:
gke-manifest-generation. - Google Cloud resources (buckets, service accounts, node pools,
clusters):
gcp-config-connectorfor KCC repositories. They can ride in the same pull request as the chart (Step 4). - A request that asked for advice, not a change ("should we use
cert-manager?"): answer it.
SOUL.md§3 item 3 draws that line.
Workflow
Step 0: A stop ends the request
Every "stop" in this skill is the answer, not a reason to look for another
way in. When one applies, report it in the words given, change nothing,
and end: on a kanban card with kanban_block(kind="needs_input") and the
stop as the reason. Do not go on to check what you are allowed to create
(kubectl auth can-i create ...), list Secrets, try another identity, or
search the filesystem for credentials or a repository; a card that says
"install and verify" is still answered by the stop.
What ships with it
3 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.
- today Changed · +10 tokens per session 45e50af6b8b4
- 2d ago First seen · 265 lines · 169 tokens per session scan A 69097fd8e78e
gitops-helm-chart is a skill published in the GitHub repository gke-labs/kube-agents (109 stars, last pushed today), licensed Apache-2.0. It adds 179 tokens to every session and 3,375 once invoked, about $0.0007 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-10-20.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Fully automate a release with version-bump and childhood.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.