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 skills add wedabro/bro-skills --skill speckit.event-realtimegit clone --depth 1 https://github.com/wedabro/bro-skillsWrote 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/wedabro/bro-skills/speckit.event-realtime)<a href="https://agentmods.dev/skills/wedabro/bro-skills/speckit.event-realtime"><img src="https://agentmods.dev/badge/skills/wedabro/bro-skills/speckit.event-realtime/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/skills/wedabro/bro-skills/speckit.event-realtime"><img src="https://agentmods.dev/badge/skills/wedabro/bro-skills/speckit.event-realtime.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.00033 | $0.00790 |
| Opus 5 | $0.00016 | $0.00395 |
| Sonnet 5 | $0.00007 | $0.00158 |
| Haiku 4.5 | $0.00003 | $0.00079 |
Grade A, and why
speckit.event-realtime 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 11d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🎯 Mission
Design and implement ultra-reliable real-time communications and event-driven distributed architectures. Ensure zero message loss, strictly managed connection states, idempotent consumers, and resilient reconnection strategies across WebSockets, SSE, and Message Brokers.
📥 Required Inputs
.agents/specs/[feature]/spec.md,plan.md, andtasks.md- Target transport (WebSocket, Server-Sent Events, Webhooks, Message Broker)
- Event schemas, ordering guarantees, and throughput requirements
📋 Protocol
1. WebSocket Architecture (Multi-Node Scaling)
- Stateless Server Nodes: Distribute WebSocket connections across multiple server instances using Redis Pub/Sub, Redis Streams, or RabbitMQ as the central message bus backplane.
- Connection Heartbeat: Implement ping/pong heartbeat every 30 seconds. Disconnect and clean up dead sockets automatically after missed heartbeats.
- Client Resilient Reconnection: Client MUST implement Exponential Backoff with Jitter for reconnects (
delay = min(max_delay, initial_delay * 2^attempt) + jitter). - Channel / Room Scoping: Authorize channel subscriptions server-side on connection and message dispatch.
2. Server-Sent Events (SSE) for Unidirectional Streams
- Use Cases: Live LLM token streaming, notification feeds, progress dashboards.
- Headers: Set
Content-Type: text/event-stream,Cache-Control: no-cache,Connection: keep-alive,X-Accel-Buffering: no(for Nginx proxy). - Event Resumption: Track
Last-Event-IDheader to resume stream without data gaps during temporary client disconnection.
3. Transactional Outbox Pattern (Zero Message Loss)
- Problem Solved: Dual-write hazard where database commit succeeds but message broker publish fails (or vice versa).
- Pattern:
- Write domain data mutation AND outbox event record within the SAME database transaction.
- Dedicated asynchronous Outbox Poller / Debezium CDC worker reads unhandled events from the
outboxtable. - Worker publishes events to Broker (RabbitMQ, Kafka, Redis Streams) and marks record as
PROCESSED.
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.
- 11d ago First seen · 55 lines · 33 tokens per session scan A 1fac9ff212f7
speckit.event-realtime is a skill published in the GitHub repository wedabro/bro-skills (2 stars, last pushed 15d ago), licensed MIT. It adds 33 tokens to every session and 790 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
mx-lookup-post-batch
Retrieve MX records for up to 50 domains in a single request. Results for each domain are sorted by priority ascending (lowest numeric value has the highest mail delivery priority per RFC 5321).
timezone-post-batch
Look up timezone information for up to 50 locations in a single request. Each item can specify a timezone name, city, or lat/lon coordinates. Priority is timezone name > city > coordinates. Results are returned in input order.
trivia-post-batch
Returns up to 50 trivia questions in a single request.
email-validate-post-email
Validates a single email address and returns a full breakdown of syntax validity, MX record status, disposable domain check, normalized form, and any typo suggestion.
unit-conversion-post-batch
Skill "unit-conversion-post-batch" from bobadilla-tech/requiems-api-skills, covering endpoint, batch convert units, parameters, request example and response example.
domain-info-get-{domain}
Returns DNS records and availability status for the given domain.