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/mapping-streaming-eventsnpx skills add LerianStudio/ring --skill mapping-streaming-eventsgit 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/mapping-streaming-events)<a href="https://agentmods.dev/skills/lerianstudio/ring/mapping-streaming-events"><img src="https://agentmods.dev/badge/skills/lerianstudio/ring/mapping-streaming-events.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 | $0.00095 | $0.03254 |
| Opus 5 | $0.00048 | $0.01627 |
| Sonnet 5 | $0.00019 | $0.00651 |
| Haiku 4.5 | $0.00010 | $0.00325 |
Grade A, and why
ring:mapping-streaming-events 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 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.
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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Streaming Event Mapping (lib-streaming, PM-team)
When to use
- User requests an event catalog, eventable-point inventory, or "where should we emit events" map
- PM team prepares a Lerian Go service for client-facing event streaming subscriptions
- Pre-flight to ring:instrumenting-streaming-events
- Task mentions "event mapping", "streaming inventory", "eventable points", "client event subscription"
Skip when
- Service is not a Go project (lib-streaming is Go-only)
- Service has no business logic to emit events about (pure infrastructure, gateway, sidecar, proxy)
- Task is purely documentation, configuration, or non-discovery
- Service is consumer-only with no outbound business event surface
Sequence
Runs before: ring:instrumenting-streaming-events
Related
Complementary: ring:instrumenting-streaming-events, ring:codebase-explorer, ring:mapping-feature-relationships
Prerequisites
- Go service codebase available for read access
- At least one entry point present (HTTP route, gRPC method, RabbitMQ consumer, scheduled job, webhook)
- Tenant identity resolvable from request context
Orchestrates 3-pass codebase discovery to produce an event catalog and instrumentation map for lib-streaming. You orchestrate. Agents explore. You NEVER read, write, or edit source code directly.
Announce at start: "Using ring:mapping-streaming-events through 7 gates (0-7)."
Streaming Architecture
lib-streaming is a producer-only, write-only event-emission library for Lerian Go services. Events are emitted via emitter.Emit(ctx, EmitRequest{DefinitionKey, TenantID, Subject, Payload}) against the streaming.Emitter interface (constructed via streaming.NewBuilder().Catalog(...).Build(ctx)). Wire format: CloudEvents 1.0 binary mode. Each RouteDefinition selects a transport — Kafka, SQS, RabbitMQ, EventBridge, or Custom. Per-tenant SaaS subscription remains the primary delivery model regardless of transport; Kafka topic naming is lerian.streaming.<resource>.<event>[.vN] with tenant carried on the ce-tenantid CloudEvents header.
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 · 258 lines · 95 tokens per session scan A 6ae42d0eb5ae
ring:mapping-streaming-events is a skill published in the GitHub repository LerianStudio/ring (211 stars, last pushed 16d ago), licensed Apache-2.0. It adds 95 tokens to every session and 3,254 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
analytics
/analytics - Agent Usage Analytics.
api-design
You are the API Design Specialist, responsible for designing RESTful, GraphQL, or other API interfaces. You ensure APIs are well-designed, documented, versioned, and follow best practices.
clean
Use this agent to strip all AI/LLM framework artifacts before production deployment.
fixer
Auto-remediation router and retry coordinator.
release
Use this agent for versioning, changelogs, release notes, deployment coordination, and release process management.
review
You are a exacting code reviewer who combines high quality standards with deep technical expertise. You only flag issues that genuinely matter - bugs, security vulnerabilities, logic errors, and violations of framework standards.