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 skills/lerianstudio/ring/using-lib-streamingnpx skills add LerianStudio/ring --skill using-lib-streaminggit 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/using-lib-streaming)<a href="https://agentmods.dev/skills/lerianstudio/ring/using-lib-streaming"><img src="https://agentmods.dev/badge/skills/lerianstudio/ring/using-lib-streaming.svg" alt="Measured on agentmods" 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.00099 | $0.10552 |
| Opus 5 | $0.00049 | $0.05276 |
| Sonnet 5 | $0.00020 | $0.02110 |
| Haiku 4.5 | $0.00010 | $0.01055 |
Grade A, and why
ring:using-lib-streaming 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 3d 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 — 750 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ring:using-lib-streaming
When to use
Sweep mode:
- "Sweep this service for lib-streaming adoption opportunities"
- "Find every DIY Kafka / SQS / RabbitMQ publisher that should use lib-streaming"
- "Audit our event publishing layer against lib-streaming"
- "We have raw franz-go / sarama / watermill — what should move to lib-streaming?"
- "Identify ad-hoc manifest or per-service circuit breakers around event publishing"
Reference mode:
- Need to understand what lib-streaming provides at the public facade
- Looking for the right
Buildersetter,Destinationhelper, or sentinel - Setting up a new service that emits CloudEvents-framed domain events
- Wiring multi-transport fan-out (Kafka primary + SQS shadow, etc.)
- Writing unit tests that depend on
streamingtest.MockEmitter - Need the canonical CloudEvents binary-mode Kafka header bytes for an interop layer
- Need to map a runtime
*EmitError/*MultiEmitErrorto an operator response
Skip when
- Working on non-Go services (lib-streaming is Go-only)
- Working on frontend code
- Service is consumer-only with no outbound business event surface — there is nothing for lib-streaming to instrument
- Service publishes only internal command queue messages — those stay on
github.com/LerianStudio/lib-commons/v5/commons/rabbitmq; lib-streaming is for past-tense business events to external subscribers
Related
- ring:instrumenting-streaming-events — end-to-end 13-gate orchestration that implements lib-streaming in a target service. Use that after
ring:mapping-streaming-eventshas produced a validateddocs/streaming/instrumentation-map.json. This skill is the adoption/reference counterpart — it does not own the implementation cycle. - ring:mapping-streaming-events — PM-side identification of eventable points; produces the catalog and instrumentation map this skill's REFERENCE MODE consumes.
- ring:using-lib-commons — lib-streaming depends on lib-commons for circuit breaker, outbox repository, App lifecycle, runtime panic instrumentation, and assertions. The CB / outbox / runtime / assert API surface lives there.
ring:using-outbox—OutboxWriter,TransactionalOutboxWriter,WithOutboxTx, and route-aware envelope replay live in the outbox skill. This skill points at the boundary but does NOT duplicate the writer / dispatcher API.ring:using-lib-observability—log.Logger,metrics.MetricsFactory, andtrace.Tracerare owned there. Builder setters consume those types; this skill links rather than re-documents.
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.
- 3d ago First seen · 750 lines · 99 tokens per session scan A a5a745c3b3c8
ring:using-lib-streaming is a skill published in the GitHub repository LerianStudio/ring (211 stars, last pushed 17d ago), licensed Apache-2.0. It adds 99 tokens to every session and 10,552 once invoked, about $0.0005 per session on Opus 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-09-03.
Other skills, from other repositories
security-audit
Comprehensive .NET security audit — OWASP vulnerability scan, NuGet vulnerability check, secrets detection, and combined severity report.
api-doc-gen
Generate or update OpenAPI specification from .NET controller attributes. Validate spec-to-code consistency. Use after adding or changing API endpoints.
execution/backend-executor
Internal: Backend Executor. Implements API routes, services, business logic, auth. Read spec and segment. Write evidence on completion.
execution/integration-executor
Internal: Integration Executor. Wires components together, connects external APIs, handles plumbing. Write evidence on completion.
memstack-automation-webhook-designer
Use this skill when the user says 'webhook', 'webhook handler', 'webhook endpoint', 'receive events', 'HMAC verification', 'idempotency', or needs secure webhook handlers with signature verification, retry handling, and dead letter queues. Do NOT use for full n8n workflows or scheduled tasks.
shopify-apps
Shopify app development - Remix, Admin API, checkout extensions.