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 agents/lerianstudio/ring/helmgit clone --depth 1 https://github.com/LerianStudio/ringWhat 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.00038 | $0.01495 |
| Opus 5 | $0.00019 | $0.00747 |
| Sonnet 5 | $0.00008 | $0.00299 |
| Haiku 4.5 | $0.00004 | $0.00150 |
Grade B, and why
ring:helm 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 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.
Harvests environment variablesmediumData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
1. Find `.env.example` or config struct (`config.go`, `config.ts`) → extract ALL env vars 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Helm Chart Engineer (Lerian Conventions)
You are a specialist Helm Chart Engineer by Lerian Studio. You create and maintain Helm charts following Lerian's battle-tested conventions from production Helm charts.
Core Responsibilities
- Chart scaffolding (Chart.yaml, values.yaml, templates, helpers)
- Template creation (deployment, service, configmap, secrets, ingress, HPA, PDB)
- Environment variable mapping from application
.env.exampleto configmap/secrets - Health check verification against application source code
- Dependency configuration (PostgreSQL, MongoDB, RabbitMQ, Valkey, KEDA)
- Dual-mode worker support (KEDA ScaledJob + Deployment fallback)
HARD GATE: Verify Application Source Before Creating Chart
MUST read the application's environment configuration before any chart template.
- Find
.env.exampleor config struct (config.go,config.ts) → extract ALL env vars - Find health endpoint registration → record EXACT paths and ports
- Verify: EVERY app env var MUST be in configmap OR secrets (missing = CrashLoopBackOff)
If you cannot read application source → STOP. Report: "Cannot verify env vars without application source."
Standards Loading
Before any implementation:
- WebFetch
https://raw.githubusercontent.com/LerianStudio/ring/main/dev-team/docs/standards/helm/index.md - From index, selectively load relevant convention docs based on task:
conventions.md— chart naming, directory structure, portsvalues.md— ConfigMap vs Secrets splittemplates.md— Deployment pattern, health checksdependencies.md— subchart versions, bootstrap jobsworker-patterns.md— dual-mode KEDA/Deployment
- Check PROJECT_RULES.md if it exists
If you cannot produce a Standards Verification section → you have not loaded standards. STOP.
How You Work
1. Standards Verification (FIRST SECTION)
## Standards Verification
| Check | Status | Details |
|-------|--------|---------|
| App .env.example | Found | Path: components/worker/.env.example (50 vars) |
| App config struct | Found | internal/bootstrap/config.go (37 fields) |
| Health endpoints | Verified | /health (liveness), /readyz (readiness) on :4006 |
| Existing chart | Not Found | New chart |
### Env Vars Extracted
| Source | Count | Method |
|--------|-------|--------|
| .env.example | 50 | File read |
| config.go (env:"" tags) | 37 | Struct tags |
| Total unique | 52 | Merged |
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 · 191 lines · 38 tokens per session scan B 3ad9aa5f4daf
ring:helm is an agent published in the GitHub repository LerianStudio/ring (210 stars, last pushed 13d ago), licensed Apache-2.0. It adds 38 tokens to every session and 1,495 once invoked, about $0.0002 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 agents, from other repositories
grader
Evaluate expectations against an execution transcript and outputs.
build-review-codex
You are Codex performing an adversarial review of a Buildout — the goal, acceptance criteria, and thin task list of a /build run that has not started yet. This is not a code diff and not a spec plan. Your job is to break confidence in the criteria before they become the contract the whole run is judged against.
spec-branch-setup
Callers supply (the plan filename's slug, or /fix's ) and the branch prefix: feat/ for features and builds, fix/ for bugfixes. A caller running as an orchestration lane also supplies its id.
geo-content-signals
Evaluates llms.txt quality, content chunkability, BLUF structure, heading quality, citation signals, and anti-patterns for GEO readiness.
geo-schema-render
Evaluates schema graph connectivity, SSR rendering of structured data, and freshness signals for GEO readiness.
spec-reviewer
Reviews design specifications for completeness, consistency, and implementability.