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/yindia/rootcause/k8s-helmnpx skills add yindia/rootcause --skill k8s-helmgit clone --depth 1 https://github.com/yindia/rootcauseWrote 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/yindia/rootcause/k8s-helm)<a href="https://agentmods.dev/skills/yindia/rootcause/k8s-helm"><img src="https://agentmods.dev/badge/skills/yindia/rootcause/k8s-helm.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.00000 | $0.01733 |
| Opus 5 | $0.00000 | $0.00866 |
| Sonnet 5 | $0.00000 | $0.00347 |
| Haiku 4.5 | $0.00000 | $0.00173 |
Grade A, and why
k8s-helm 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 5d 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: k8s-helm
Helm lifecycle operations for Kubernetes using RootCause MCP tool names only.
This skill is evidence-first and safety-first.
helm.diff_release is mandatory before any mutating action.
Purpose
Use this skill for:
- repository setup,
- chart discovery and version selection,
- release install and upgrade,
- rollback planning and recovery,
- uninstall and cleanup validation,
- template apply/uninstall workflows.
Strict Tooling Contract
Use only these Helm tool names:
helm.repo_addhelm.repo_listhelm.repo_updatehelm.list_chartshelm.get_charthelm.search_chartshelm.listhelm.statushelm.diff_releasehelm.rollback_advisorhelm.installhelm.upgradehelm.uninstallhelm.template_applyhelm.template_uninstall
Use these Kubernetes inspection tools when validating releases:
k8s.describek8s.listk8s.eventsk8s.events_timelinek8s.get
Never emit kubectl-alias tool names. Never emit non-RootCause Helm naming variants.
Triggers
Enable when user intent includes:
- install chart,
- upgrade release,
- rollback failed deployment,
- resolve Helm release errors,
- inspect chart versions,
- remove a release,
- debug values not applying.
Common terms:
- helm, chart, release, values, repository,
- pending-install, pending-upgrade, failed,
- cannot re-use a name,
- immutable selector,
- another operation in progress.
Priority Rules
- State first, mutation later.
- Start with
helm.listorhelm.status.
- Diff before every mutating operation.
- Run
helm.diff_releasebefore:helm.installhelm.upgradehelm.uninstallhelm.template_applyhelm.template_uninstall
- Recovery planning before rollback.
- Run
helm.rollback_advisorfor safer target selection.
- Confirmation requirements are mandatory.
- Use
confirm=truefor tools that require it.
- Post-action verification is mandatory.
- Validate with
helm.statusandk8s.*evidence tools.
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.
- 5d ago First seen · 261 lines · 0 tokens per session scan A 2df6e925a38e
k8s-helm is a skill published in the GitHub repository yindia/rootcause (42 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,733 tokens. 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-30.
Other skills, from other repositories
helm
Skill "helm" from chaterm/terminal-skills, covering helm 包管理, 概述, 基础命令, 仓库管理 and 添加仓库.
bazel-k8s-expert
Expert knowledge for deploying Quarkus/Java applications to Kubernetes using Bazel. Covers rulesk8s, Helm, Kustomize, ConfigMaps, Secrets, and health probes.
k8s-deployer
Kubernetes deployment management - generate manifests, Helm charts, manage rollouts, check cluster status, and apply security best practices.
k8s-ingress-gateway
Kubernetes Ingress 配置错误、Gateway 不通的完整诊断-修复-验证 Skill.
kubernetes-operator
Deploy and manage applications on Kubernetes. Covers deployments, services, ingress, HPA, secrets, and production-grade cluster configuration.
dependabot-batch
Use when reviewing Radar's weekly Dependabot PRs and replacing the safe, 72-hour-soaked updates with one changelog-vetted, tested PR.