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 LerianStudio/ring --skill creating-helm-chartsgit clone --depth 1 https://github.com/LerianStudio/ringWrote 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/lerianstudio/ring/creating-helm-charts)<a href="https://agentmods.dev/skills/lerianstudio/ring/creating-helm-charts"><img src="https://agentmods.dev/badge/skills/lerianstudio/ring/creating-helm-charts.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 75 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00092 | $0.01146 |
| Opus 5 | $0.00046 | $0.00573 |
| Sonnet 5 | $0.00018 | $0.00229 |
| Haiku 4.5 | $0.00009 | $0.00115 |
Grade B, and why
ring:creating-helm-charts scanned grade B with 1 finding 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 8d 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.
Harvests environment variablesmediumData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
— extract ALL env vars (missing vars = CrashLoopBackOff) Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Helm Chart Creation & Maintenance
When to use
- Creating a new Helm chart for any Lerian service
- Modifying an existing Helm chart (adding components, dependencies, templates)
- Reviewing a Helm chart PR for convention compliance
- Migrating a docker-compose setup to Helm
Skip when
- Modifying only application code (no chart changes)
- Working on non-Helm deployment (docker-compose only) → use backend engineer via ring:implementing-tasks
Sequence
Standalone/on-demand. Not part of the lean backend dev-cycle.
Related
Complementary: ring:implementing-tasks
Standards reference: dev-team/docs/standards/helm/
Executor agent: ring:helm
You orchestrate. ring:helm creates chart files.
Step 1: Validate Input
Required: service_name, chart_type (single|multi-component|umbrella), components (non-empty).
Optional: dependencies (postgresql, mongodb, rabbitmq, valkey, keda), has_worker, namespace.
Step 2: Naming Convention
Default: {service_name}-helm (e.g., reporter-helm, tracer-helm)
Exceptions (no -helm suffix):
- plugin-access-manager
- otel-collector-lerian
Step 3: Dispatch Agent
Task:
subagent_type: "ring:helm"
description: "Create Helm chart for {service_name}"
prompt: |
## Helm Chart Creation
service_name: {service_name}
components: {components}
dependencies: {dependencies}
chart_type: {chart_type}
namespace: {namespace}
Standards: Load dev-team/docs/standards/helm/ files.
## Required Steps
1. Read application .env.example and bootstrap/config.go
— extract ALL env vars (missing vars = CrashLoopBackOff)
2. Verify health check endpoint in application source
3. Create chart structure:
charts/{service_name}-helm/
├── Chart.yaml
├── values.yaml
├── templates/
│ ├── _helpers.tpl
│ ├── deployment.yaml
│ ├── service.yaml
│ ├── configmap.yaml
│ ├── secret.yaml (if secrets exist)
│ ├── hpa.yaml (optional)
│ └── serviceaccount.yaml
└── charts/ (dependencies)
4. Chart.yaml: name, version, appVersion, description, type: application
5. _helpers.tpl: name, fullname, chart, labels, selectorLabels, versionLabelValue
6. values.yaml structure:
- global: replicaCount, image.repository/tag/pullPolicy
- Per-component config sections
- configmap: all non-secret env vars
- secrets: all sensitive env vars (no real values)
- service: type: ClusterIP, port, targetPort
- resources: requests/limits
- probes: livenessProbe, readinessProbe (match /health and /readyz)
- dependencies config sections
7. Security defaults:
- securityContext: runAsNonRoot: true, runAsUser: 1000
- readOnlyRootFilesystem: true
- allowPrivilegeEscalation: false
8. Service type: ALWAYS ClusterIP (never NodePort or LoadBalancer)
## Required Output
- Env Var Coverage table (100% of .env.example covered)
- helm lint result: MUST PASS
- helm template render: MUST produce valid YAML
- Files created list
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.
- 8d ago First seen · 142 lines · 92 tokens per session scan B ca91d46dee92
ring:creating-helm-charts is a skill published in the GitHub repository LerianStudio/ring (211 stars, last pushed 19d ago), licensed Apache-2.0. It adds 92 tokens to every session and 1,146 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (harvests environment variables). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
staging-deploy
Build, push, migrate, and deploy to staging environment with health check verification. Use when deploying a completed phase to staging.
azure-sweep
Runs the full 8-layer Azure governance sweep using the Azure Sweeper agent.
infra-deploy
Validate, what-if/plan, deploy, and verify Azure infrastructure using Bicep, Terraform, or azd. Use when deploying a completed infrastructure phase to an environment.
ds-deploy
Deployment and infrastructure — containerization, deployment, monitoring, incident response. Use when deploying an app, setting up containers/monitoring, or planning incident response.
execution/infra-executor
Internal: Infrastructure Executor. Implements deployment, CI/CD, container, IaC, and environment configuration changes. Write evidence on completion.
memstack-deployment-docker-setup
Use this skill when the user says 'Docker', 'Dockerfile', 'docker-compose', 'containerize', 'docker-setup', or needs to containerize an application with optimized Docker images and compose configurations. Do NOT use for serverless or static site deployments.