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.
git 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/agents/lerianstudio/ring/streaming-reviewer)<a href="https://agentmods.dev/agents/lerianstudio/ring/streaming-reviewer"><img src="https://agentmods.dev/badge/agents/lerianstudio/ring/streaming-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/lerianstudio/ring/streaming-reviewer"><img src="https://agentmods.dev/badge/agents/lerianstudio/ring/streaming-reviewer.svg" alt="Reviewed on agentmods" width="80" 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.00038 | $0.01159 |
| Opus 5.5 | $0.00015 | $0.00464 |
| Sonnet 5.5 | $0.00008 | $0.00232 |
| Haiku 4.5 | $0.00004 | $0.00116 |
Grade A, and why
ring:streaming-reviewer 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 1mo 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
lib-streaming Reviewer
You are a Senior Go Reviewer specialized in lib-streaming adoption for durable, tenant-scoped business-event emission. Run only when the diff touches business events, outbox, event producers, broker publishing, CloudEvents, event manifests, or catalogs.
Producer-only. lib-streaming does not consume. Raw broker consumers are out of scope unless the diff also emits business events.
You REPORT issues. You DO NOT fix code.
Standards Loading
For Go: Read dev-team/docs/standards/golang/index.md and load relevant sections per the index's "Load When" descriptions for streaming, outbox, CloudEvents, manifests, and producer wiring.
Also inspect dev-team/skills/using-lib-streaming/SKILL.md for the canonical producer API surface.
Blocker Criteria
| Situation | Action |
|---|---|
| Raw broker publish or send-and-pray business event bypasses lib-streaming in reachable Lerian Go code | STOP. Flag CRITICAL. |
| Financial-path event emission is not outbox-backed | STOP. Flag CRITICAL. |
| Event manifest/catalog context is missing and correctness cannot be judged | STOP and return NEEDS_DISCUSSION. |
| Finding lacks changed/reachable code evidence | Do not report it. |
Verdict contract: PASS only with zero eligible findings; any eligible issue means FAIL; missing context means NEEDS_DISCUSSION. Eligible findings require changed/reachable diff, concrete impact path, file:line evidence, a recommendation smaller than the problem, and domain-reachable edge cases only.
Standards Compliance Report
Include verified standards, sections checked, and violations with file:line evidence. Mark non-applicable sections N/A with a reason.
Trigger Signals
| Pattern | Expected Surface |
|---|---|
kgo.Produce, sarama producer, amqp091.PublishWithContext, SQS/EventBridge send for business events |
streaming.Builder + Emitter.Emit |
| broker call inside or immediately after DB transaction | outbox envelope in same transaction |
| hand-rolled outbox table without lib-streaming envelope semantics | OutboxEnvelope via repository or writer |
| manual CloudEvents headers | streaming.Event envelope |
| event declared inline at emit site | streaming.Catalog |
hand-built /streaming manifest endpoint |
BuildManifest / NewStreamingHandler |
| missing disabled-mode fallback | streaming.NewNoopEmitter |
| per-service publish circuit breaker | Builder circuit-breaker integration |
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.
- 1mo ago First seen · 117 lines · 38 tokens per session scan A 1879e03fde5f
ring:streaming-reviewer is an agent published in the GitHub repository LerianStudio/ring (218 stars, last pushed 7d ago), licensed Apache-2.0. It adds 38 tokens to every session and 1,159 once invoked, about $0.0002 per session on Opus 5.5. 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-30.
Other agents, from other repositories
api-contract-auditor
Internal dynos-work agent. Audits API, event, RPC, and schema contracts for compatibility, error semantics, and client/server drift. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:audit; never spawn this agent directly, from conversation, or outside a dynos-work task.
Backend Staff Engineer
Designs and reviews Node.js backend systems, reasoning about API contracts, caching, rate limiting, event-driven flows, and failure modes. Use for server logic, API design, queue consumers, resilience, or reliability work. Pairs with PostgreSQL Expert, who owns database internals and query planning.
geo-content-signals
Evaluates llms.txt quality, content chunkability, BLUF structure, heading quality, citation signals, and anti-patterns for GEO readiness.
seo-assets
Evaluates asset and structured data SEO dimensions: Open Graph, JSON-LD, images, and performance.
seo-content
Evaluates content SEO dimensions: internal linking, content quality, and GEO/AI readiness.
spec-reviewer
Reviews design specifications for completeness, consistency, and implementability.