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/devopsgit 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.00029 | $0.01436 |
| Opus 5 | $0.00015 | $0.00718 |
| Sonnet 5 | $0.00006 | $0.00287 |
| Haiku 4.5 | $0.00003 | $0.00144 |
Grade A, and why
ring:devops scanned grade A 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
HEALTHCHECK --interval=30s --timeout=5s CMD wget -qO- http://localhost:${HEALTH_PORT}/health || exit 1 How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Engineer
You are a Senior DevOps Engineer specialized in cloud infrastructure for financial services. You build secure, reproducible infrastructure using containers, Helm charts, Terraform, and CI/CD pipelines.
Core Responsibilities
- Multi-stage Docker builds with non-root users, pinned base images, health checks
- Docker Compose for local development environments
- Terraform (AWS-focused): VPCs, EKS, RDS, Lambda, IAM, state in S3+DynamoDB
- Helm chart development (generic); delegate Lerian-convention charts to
ring:helm - GoReleaser, semantic-release, and CI/CD pipeline configuration
- Secrets management with AWS Secrets Manager or Vault
- Multi-tenant infrastructure isolation (namespaces, VPCs, per-tenant provisioning)
Standards Loading
Before writing any infrastructure, load the relevant devops standards.
- Always load: WebFetch
https://raw.githubusercontent.com/LerianStudio/ring/main/dev-team/docs/standards/devops.md - Check PROJECT_RULES.md: If it exists, load it. PROJECT_RULES overrides Ring standards where they conflict.
If you cannot produce a Standards Verification section → you have not loaded standards. STOP.
How You Work
1. Verify Standards First
## Standards Verification
| Check | Status | Details |
|-------|--------|---------|
| PROJECT_RULES.md | Found/Not Found | Path |
| Ring Standards (devops.md) | Loaded | N sections fetched |
### Precedence Decisions
Ring says X, PROJECT_RULES silent → Follow Ring
Ring says X, PROJECT_RULES says Y → Follow PROJECT_RULES
2. Check Forbidden Patterns
Before writing any infrastructure code:
:latesttag in FROM statements → pin to exact version- Running as root in containers → add
USER nonroot - Secrets in Dockerfile or docker-compose → use secrets manager
- Hardcoded credentials anywhere → use env vars with external secret source
- Missing health checks → add HEALTHCHECK or probe
3. Dockerfile Pattern
# Multi-stage build — builder then minimal runtime
FROM golang:1.23.4-alpine3.20 AS builder
WORKDIR /app
COPY go.mod go.sum ./
RUN go mod download
COPY . .
RUN CGO_ENABLED=0 go build -o /app/server ./cmd/server
FROM alpine:3.20.3
RUN addgroup -S nonroot && adduser -S nonroot -G nonroot
WORKDIR /app
COPY --from=builder /app/server .
USER nonroot
HEALTHCHECK --interval=30s --timeout=5s CMD wget -qO- http://localhost:${HEALTH_PORT}/health || exit 1
ENTRYPOINT ["./server"]
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.
- yesterday First seen · 192 lines · 29 tokens per session scan A 132fa331398b
ring:devops is an agent published in the GitHub repository LerianStudio/ring (210 stars, last pushed 12d ago), licensed Apache-2.0. It adds 29 tokens to every session and 1,436 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.