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/lukasrepublic/agentic-foundry/helm-k8s-patternsnpx skills add lukasrepublic/agentic-foundry --skill helm-k8s-patternsgit clone --depth 1 https://github.com/lukasrepublic/agentic-foundryWrote 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/lukasrepublic/agentic-foundry/helm-k8s-patterns)<a href="https://agentmods.dev/skills/lukasrepublic/agentic-foundry/helm-k8s-patterns"><img src="https://agentmods.dev/badge/skills/lukasrepublic/agentic-foundry/helm-k8s-patterns.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.1 | $0.00000 | $0.01518 |
| Opus 5 | $0.00000 | $0.00759 |
| Sonnet 5 | $0.00000 | $0.00304 |
| Haiku 4.5 | $0.00000 | $0.00152 |
Grade A, and why
helm-k8s-patterns 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to trigger
- Authoring a new Helm chart or modifying an existing one in the IaC repo's charts tree.
- Authoring or modifying per-environment values files.
- Secret-reference work via an external-secrets operator.
- A deployment-strategy choice (RollingUpdate vs. canary vs. blue-green).
- Probe authoring (readinessProbe, livenessProbe, startupProbe).
- RBAC changes (ServiceAccount, Role, RoleBinding, ClusterRole, ClusterRoleBinding).
- HPA, PDB, or PVC authoring.
Procedure
-
Chart structure under the charts tree's
<name>/:Chart.yaml+values.yaml(defaults) + per-environment values files + atemplates/directory. Read the existing chart structure before modifying — follow the naming and indentation conventions used in sibling charts. -
Secret references via external-secrets: never inline secret values in values files. Use an
ExternalSecretresource that references the secret name in the secret manager. Thevalues.yamlholds only the secret-name path; the external-secrets controller resolves the value at deploy time. -
Deployment strategy: default to
RollingUpdatewithmaxUnavailable: 0andmaxSurge: 1. Canary or blue-green strategies are authored only when the spec explicitly requires them — they add operational complexity that must be justified. -
Probe defaults (all three required for production workloads):
readinessProbe: HTTP GET on the health endpoint;initialDelaySeconds: 5,periodSeconds: 10.livenessProbe: HTTP GET on the liveness endpoint;initialDelaySeconds: 15,periodSeconds: 20.startupProbe: for slow-starting workloads (e.g., a migration runner);failureThreshold: 30,periodSeconds: 10.
-
Pre-change render sequence: lint the chart (schema + YAML validation), then render the templates with the target environment's values and eyeball the output, then diff the rendered release against the running cluster before a production-bound change. Lint and render are CI-safe and run in CI; the cluster diff requires cluster access and is operator-run.
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 · 75 lines · 0 tokens per session scan A 14807fbbf273
helm-k8s-patterns is a skill published in the GitHub repository lukasrepublic/agentic-foundry (1 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,518 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-31.
Other skills, from other repositories
scaffold
Bootstrap a new project with your stack, auth, database, and standards pre-configured.
devops
Generate Dockerfiles, GitLab CI pipelines, K8s configs, and deployment setups.
local-env-orchestration
Orchestrates local Kubernetes development environment management.
kelos
Install and configure Kelos; author, document, inspect, troubleshoot, and operate its Kubernetes custom resources and CRD schemas in the kelos.dev API group using manifests, kubectl, or the kelos CLI. Use when a request names Kelos or a distinctive Kelos kind such as AgentConfig or TaskSpawner and concerns an…
nemo-mbridge-multi-node-slurm
Convert single-node scripts to multi-node Slurm sbatch jobs and debug common multi-node failures. Covers srun-native vs uv run torch.distributed approaches, container setup, NCCL timeouts, OOM sizing for MoE models, and interactive allocation.
module-scaffold
Given a component name, generate a complete standalone ODH module operator repository. Produces Go module, CRD types implementing PlatformObject, controller skeleton with reconciler builder pattern, Helm chart, Makefile, CI config, singleton webhook, and AGENTS.md. Use when starting a new module from scratch.