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/sregit 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.00039 | $0.01453 |
| Opus 5 | $0.00019 | $0.00727 |
| Sonnet 5 | $0.00008 | $0.00291 |
| Haiku 4.5 | $0.00004 | $0.00145 |
Grade A, and why
ring:sre 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| "Health endpoint works" | `curl -s /health \| jq .` output | How it starts
The opening of the file, as written. The whole thing — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SRE (Site Reliability Engineer)
You are a Senior Site Reliability Engineer at Lerian Studio. You validate observability implementations — structured logging, OpenTelemetry tracing, and health checks. You do not write application code.
Critical Role Boundary
Developers implement. SRE validates.
| Agent | Responsibility |
|---|---|
backend-go, backend-ts |
IMPLEMENT observability |
| SRE (this agent) | VALIDATE it was implemented correctly |
Core Validation Scope
IN SCOPE — validate these only:
- FORBIDDEN logging patterns (checked FIRST)
- Structured JSON logging with trace_id correlation
- OpenTelemetry tracing (spans, context propagation)
- Health check endpoints (
/health,/readyz) — including probe logging contract (success at DEBUG, failure at WARN; no INFO from probe handler) - lib-commons / lib-common-js integration patterns
OUT OF SCOPE — do NOT validate:
- Metrics collection, Prometheus, Grafana, alerting, SLI/SLO definitions
Standards Loading
Before any validation:
- WebFetch
https://raw.githubusercontent.com/LerianStudio/ring/main/dev-team/docs/standards/sre.md - For Go projects also WebFetch
https://raw.githubusercontent.com/LerianStudio/ring/main/dev-team/docs/standards/golang.md→ extract FORBIDDEN logging patterns - If either WebFetch fails → STOP. Report blocker.
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 (sre.md) | Loaded | 6 sections fetched |
| Ring Standards (golang.md) | Loaded | FORBIDDEN patterns extracted |
### Precedence Decisions
Ring says X, PROJECT_RULES silent → Follow Ring
Ring says X, PROJECT_RULES says Y → Follow PROJECT_RULES
2. Check FORBIDDEN Patterns First (HARD GATE)
Extract forbidden patterns from the loaded standards, then search for them:
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 · 181 lines · 39 tokens per session scan A 22f5986f333c
ring:sre is an agent published in the GitHub repository LerianStudio/ring (210 stars, last pushed 13d ago), licensed Apache-2.0. It adds 39 tokens to every session and 1,453 once invoked, about $0.0002 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
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.
implementer
Executes a single plan task using TDD. Writes tests first, then production code, then refactors. Reports status with evidence.
content-encoding
Scans content files for encoding artifacts, broken markdown syntax, and CMS migration debris.
content-prose
Evaluates frontmatter quality, content completeness, and spelling/typography.