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 LuuOW/meridian-mcp --skill event-drivengit clone --depth 1 https://github.com/LuuOW/meridian-mcpWrote 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/luuow/meridian-mcp/event-driven)<a href="https://agentmods.dev/skills/luuow/meridian-mcp/event-driven"><img src="https://agentmods.dev/badge/skills/luuow/meridian-mcp/event-driven.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.00034 | $0.01881 |
| Opus 5 | $0.00017 | $0.00941 |
| Sonnet 5 | $0.00007 | $0.00376 |
| Haiku 4.5 | $0.00003 | $0.00188 |
Grade A, and why
event-driven 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 7d 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
event-driven
Covers how to design, implement, and operate event-driven systems: pub/sub messaging, event buses, async pipelines, and reactive coordination between services.
1) Redis pub/sub fundamentals
import redis.asyncio as aioredis
import asyncio, json
redis = aioredis.from_url("redis://localhost:6379", decode_responses=True)
# Publisher
async def publish(channel: str, event: dict):
await redis.publish(channel, json.dumps({**event, "_ts": asyncio.get_event_loop().time()}))
# Subscriber (persistent listener)
async def subscribe(channels: list[str], handler):
async with redis.pubsub() as pubsub:
await pubsub.subscribe(*channels)
async for message in pubsub.listen():
if message["type"] == "message":
await handler(json.loads(message["data"]))
2) Event bus abstraction
from collections import defaultdict
from typing import Callable, Awaitable
EventHandler = Callable[[dict], Awaitable[None]]
class EventBus:
def __init__(self):
self._handlers: dict[str, list[EventHandler]] = defaultdict(list)
def on(self, event_type: str):
"""Decorator to register a handler."""
def decorator(fn: EventHandler) -> EventHandler:
self._handlers[event_type].append(fn)
return fn
return decorator
async def emit(self, event_type: str, payload: dict):
for handler in self._handlers.get(event_type, []):
await handler({"type": event_type, **payload})
async def emit_all(self, events: list[tuple[str, dict]]):
"""Emit multiple events concurrently."""
await asyncio.gather(*[self.emit(t, p) for t, p in events])
bus = EventBus()
@bus.on("article.published")
async def on_article_published(event: dict):
await index_article(event["slug"])
@bus.on("article.published")
async def notify_subscribers(event: dict):
await send_notification(event["slug"])
3) Durable event queue (Redis Streams)
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.
- 7d ago First seen · 222 lines · 34 tokens per session scan A ae91e671c8c8
event-driven is a skill published in the GitHub repository LuuOW/meridian-mcp (0 stars, last pushed 3d ago), licensed MIT. It adds 34 tokens to every session and 1,881 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
backend-cqrs-patterns
Use this skill when the user says 'CQRS', 'command query segregation', 'separate read write model', 'command model', 'query model', 'read model', 'write model', 'materialized view', 'command handler', 'query handler'. This skill enforces: strict command/query separation, write model optimized for consistency, read…
effect-batching
Implement automatic request batching and deduplication using Effect's Request, RequestResolver, and SqlResolver APIs. Use this skill when solving N+1 query problems, building batched data-fetching layers, or integrating request caching with resolvers.
Cache Strategy Consistency Guard
Detect undefined or inconsistent cache strategies (layers, consistency, invalidation, TTL, failure handling) in design documents.
performant-laravel
Strategies for high-performance, scalable Laravel systems (Octane, DB Optimization, Redis, Microservices).
redis-state-management
Comprehensive guide for Redis state management including caching strategies, session management, pub/sub patterns, distributed locks, and data structures.
event-driven-topology-selector
Choose between broker and mediator event-driven topologies based on workflow control needs, error handling requirements, and performance trade-offs. Use this skill whenever the user is designing an event-driven system, choosing between choreography and orchestration, deciding how events should flow between processors…