- Home
- Skills
- DevOps & Cloud
- Helm Chart Safety Check
More screenshots
Works with the AI Agents you already use
Helm Chart Safety Check
And {{ randAlphaNum 32 }} in a Secret without lookup quietly changes the database password on every helm upgrade.
$5
Helm Chart Safety Check
Example session with this skill installed
Check this project with helm-chart-safety-check.
- Read your context and instructions
- Compiled the helm chart safety
$ python3 scripts/check_helm.py examples/risky
BLOCK shop/templates/deployment.yaml:29 H01 SECRET_IN_CHART
STRIPE_API_KEY=<redacted, 31 chars>
Why: A password, token or key is written into the chart: in a values file, in a template (a Secret's data or stringData, an env value, a template variable), as a | default "..." fallback for a secret value or inside a Secret's data, or as a password inside a URL. Values files and templates are packaged and pushed with the chart, so everyone who can pull the chart or read the repository has the secret, and a default is used by every install that does not override it.
Safer: Rotate the secret. Leave the value empty and make the template stop without it ({{ required "auth.password is required" .Values.auth.password }}), or point at a Secret created outside the chart (existingSecret, filled by External Secrets, Sealed Secrets, SOPS or helm-secrets). Pass real values at install time from a file that is not committed.
BLOCK shop/templates/log-agent-daemonset.yaml:30 H03 HOSTPATH_RUNTIME_OR_ROOT
BLOCK shop/templates/secret.yaml:7 H01 SECRET_IN_CHART
BLOCK shop/values.yaml:11 H01 SECRET_IN_CHART
BLOCK shop/values.yaml:15 H01 SECRET_IN_CHART
BLOCK shop/values.yaml:43 H02 PRIVILEGED_CONTAINER
REVIEW shop/Chart.yaml:6 H11 UNPINNED_IMAGE
REVIEW shop/Chart.yaml:9 H15 DEPENDENCY_NOT_PINNED
REVIEW shop/Chart.yaml:10 H16 DEPENDENCY_OVER_HTTP
REVIEW shop/Chart.yaml:13 H15 DEPENDENCY_NOT_PINNED
REVIEW shop/templates/ingress.yaml:3 H18 INGRESS_WITHOUT_TLS
REVIEW shop/templates/log-agent-daemonset.yaml:16 H13 NO_MEMORY_LIMIT
REVIEW shop/templates/log-agent-daemonset.yaml:33 H12 HOST_ACCESS
REVIEW shop/templates/secret.yaml:8 H19 SECRET_REGENERATED_ON_UPGRADE
REVIEW shop/values.yaml:7 H11 UNPINNED_IMAGE
REVIEW shop/values.yaml:20 H14 ROOT_ALLOWED
REVIEW shop/values.yaml:23 H17 PUBLIC_LOADBALANCER
REVIEW shop/values.yaml:34 H18 INGRESS_WITHOUT_TLS
REVIEW shop/values.yaml:36 H13 NO_MEMORY_LIMIT
REVIEW shop/values.yaml:41 H12 HOST_ACCESS
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 9 files, 9 with Helm chart content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
A chart that ships adminPassword: changeme123 in values.yaml, or {{ .Values.auth.password | default "admin" }} in a Secret template, hands that password to every install that does not override it and to everyone who can pull the chart. And {{ randAlphaNum 32 }} in a Secret without lookup quietly changes the database password on every helm upgrade. This skill finds those and ten other Helm chart mistakes before the chart is published or installed, and tells you how to fix each one.
Your agent runs a scanner on your chart: Chart.yaml, requirements.yaml, values.yaml and other values files, and the .yaml, .yml and .tpl files in templates/ (subcharts in charts/ too). Chart.yaml and values files are read as YAML. Templates hold Go template code that is not valid YAML, so they are read line by line, skipping {{/* */}} and # comments and telling values written out in the file from {{ ... }} references. It knows Helm conventions such as an empty image tag that falls back to appVersion, existingSecret and passwordKey names, components switched off with enabled: false, Bitnami resourcesPreset and helm test pods, so a fresh helm create chart gets only the review points it really has. It never runs helm, renders templates or connects to a cluster. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.
What it checks
BLOCK
- H01: passwords, tokens and keys in values files and templates: secret-named keys, env values, literal Secret data, | default "..." fallbacks for secret values or inside a Secret's data, private keys and passwords in URLs
- H02: privileged: true in a template or values file
- H03: hostPath mounts of the Docker, containerd or CRI-O socket, or of the node root without readOnly
REVIEW
- H11: tag: latest, images without a tag, default "latest" in templates and appVersion: latest (helm test pods are skipped)
- H12: hostNetwork, hostPID, hostIPC and other hostPath mounts, including a read-only mount of the node root as node exporters use
- H13: no memory limit in the default values, or workload templates with no resources block
- H14: containers that may run as root: runAsUser: 0, no runAsNonRoot in the default values, templates with no securityContext
- H15: dependencies from a chart repository with no version or an open-ended range (*, >=); local file:// subcharts are skipped
- H16: dependencies from plain http:// repositories
- H17: Services of type LoadBalancer without source ranges or an internal load balancer annotation
- H18: ingresses turned on without TLS, and Ingress templates with no tls section
- H19: Secrets generated with randAlphaNum, uuidv4 or genCA in a file that never uses lookup, so they change on every upgrade
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason and safer approach for each rule
- A risky and a safe example chart (Chart.yaml, values.yaml, deployment, secret, service, ingress, DaemonSet and test templates), and the real report the scanner produces on the risky one
Limits It reads the chart's files as written and does not render templates: values passed with --set or -f at install time, logic inside if and range blocks, named templates from other files and the defaults of subcharts that are not in the folder are not followed. Rendered manifests and the live cluster are not checked. NOT FLAGGED is not a guarantee.
Static check of Helm chart text (Chart.yaml, requirements.yaml, values files and templates). Templates are not rendered, and install-time values, admission policies and the cluster itself are not checked. NOT FLAGGED is not a guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 5 days ago
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example chart includes clearly fake, inert passwords and keys (NOTREAL-...) for the scanner to find. It is never installed.