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/fold-run/fold/helm-chartnpx skills add fold-run/fold --skill helm-chartgit clone --depth 1 https://github.com/fold-run/foldWhat 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.00061 | $0.01071 |
| Opus 5 | $0.00030 | $0.00535 |
| Sonnet 5 | $0.00012 | $0.00214 |
| Haiku 4.5 | $0.00006 | $0.00107 |
Grade A, and why
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 2d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changing the Helm chart
deploy/helm/fold is a published artifact: the release workflow packages it
to oci://ghcr.io/fold-run/charts/fold and attests its provenance. A
published OCI tag is immutable, so a mistake here cannot be amended in
place — only superseded.
The gate
make helm-check
Three things, and the third is the one people forget exists:
helm lintagainstci/default-values.yaml.helm templateagainst everyci/*.yaml, with--api-versions monitoring.coreos.com/v1so the ServiceMonitor renders without a cluster.- The required-config guard: rendering with no config must fail.
A chart that installs with no upstreams would start a gateway that
federates nothing, so the failure is the feature. If your change makes a
bare
helm templatesucceed, you have broken it.
Not part of make check — it needs helm on PATH, and the contributor
toolchain stays Go-only. CI runs it as its own helm job.
The three ci values files are three deployment shapes
They are not examples; they are the render matrix. A new value should be exercised by at least one, and a value that changes rendering in a shape none of them covers needs a fourth or an extension to one.
| File | Shape it pins |
|---|---|
default-values.yaml |
Minimal: inline config, no allowedHosts |
existing-configmap-values.yaml |
Operator-managed ConfigMap, Redis by URL |
full-values.yaml |
Ingress, HPA, PDB, ServiceMonitor, Redis via secret, secrets via envFrom |
The probe Host-header trap
fold's DNS-rebinding protection covers /health like every other path, so
a kubelet probe carries a Host the allowlist must admit. The chart
resolves this three different ways, and each ci file exists to pin one:
- No
allowedHosts→ the probe Host falls back tolocalhost. allowedHostsset → it derives fromallowedHosts[0].existingConfigMap→probes.hostHeaderis mandatory, because the chart cannot see inside an operator's ConfigMap to find the allowlist.
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.
- 2d ago First seen · 99 lines · 61 tokens per session scan A ce6e85692abf
helm-chart is a skill published in the GitHub repository fold-run/fold (1 stars, last pushed 2d ago), licensed Apache-2.0. It adds 61 tokens to every session and 1,071 once invoked, about $0.0003 per session on Opus 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-08-31.
Other skills, from other repositories
nginx-to-higress-migration
Migrate from ingress-nginx to Higress in Kubernetes environments. Use when (1) analyzing existing ingress-nginx setup (2) reading nginx Ingress resources and ConfigMaps (3) installing Higress via helm with proper ingressClass (4) identifying unsupported nginx annotations (5) generating WASM plugins for nginx…
helm-update
Apply helm chart updates for Bifrost. Detects config.schema.json changes since the last helm release, applies user-requested changes, updates values.yaml / values.schema.json / helpers.tpl, bumps Chart.yaml version, updates helm README (Latest Version + Upcoming section), creates a docs MDX changelog, and updates…
plano-deployment-security
Apply Plano deployment and production security practices. Use for Docker networking, state storage choices, readiness checks, and environment-based secret handling.
ecspresso
ECS deployment tool - deploy, manage, and troubleshoot ECS services.
pvetui-cli
Use when querying or managing a Proxmox VE cluster via the pvetui CLI — listing nodes, guests, and tasks; creating and migrating VMs and LXC containers; managing storage content, downloading templates and OCI images, restoring backups, and installing Proxmox Community Scripts when the plugin is enabled. Requires…
osx-tuning
Tune macOS resource limits and sysctls for best performance with Go development, Docker/OrbStack, and Linux VMs. Use this skill whenever the user asks to "tune macOS", "raise file descriptor limits", "fix ulimit", "optimize for Docker/Go/VM performance", "increase maxfiles/maxproc/somaxconn", or reports…