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 j4flmao/agent-skills --skill event-driven-architecturegit clone --depth 1 https://github.com/j4flmao/agent-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/j4flmao/agent-skills/event-driven-architecture)<a href="https://agentmods.dev/skills/j4flmao/agent-skills/event-driven-architecture"><img src="https://agentmods.dev/badge/skills/j4flmao/agent-skills/event-driven-architecture/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/j4flmao/agent-skills/event-driven-architecture"><img src="https://agentmods.dev/badge/skills/j4flmao/agent-skills/event-driven-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00161 | $0.02249 |
| Opus 5.5 | $0.00064 | $0.00900 |
| Sonnet 5.5 | $0.00032 | $0.00450 |
| Haiku 4.5 | $0.00016 | $0.00225 |
Grade A, and why
backend-event-driven-architecture 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 today.
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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Event-Driven Architecture
Purpose
Decouple services by having producers publish facts ("OrderPlaced") to a broker and consumers react independently. The skill covers the design decisions that make this reliable in practice: what goes in an event, how ordering and delivery guarantees work, and how consumers stay correct under redelivery.
Agent Protocol
Trigger
Exact user phrases: "event-driven architecture", "EDA", "publish domain events", "kafka producer", "kafka consumer", "rabbitmq exchange", "event broker", "at-least-once delivery", "event ordering", "consumer group".
Input Context
- Business flow and which services produce/consume.
- Broker in use or candidates (Kafka, RabbitMQ, cloud: SNS/SQS, Pub/Sub, Event Hubs).
- Ordering, latency and replay requirements.
- Language and client library.
Output Artifact
Event catalogue, topology (topics/exchanges, keys, consumer groups), and producer/consumer code. No files unless requested.
Response Format
Event: {PastTenseName} v{n} Key: {partition key}
Topic/Exchange: {name} Producers: {svc} Consumers: {svc,...}
Delivery: at-least-once Ordering: per {key}
Consumer idempotency: {dedupe table | natural upsert}
Failure: retry {n} with backoff -> DLQ {name}
Core Concepts
| Concept | Meaning |
|---|---|
| Event notification | Thin event ("OrderPlaced id=42"); consumers call back for details. Low coupling on schema, higher coupling at runtime |
| Event-carried state transfer | Event carries the data consumers need; no callback; larger payloads, schema is a contract |
| Command vs event | Command = request to one handler ("ChargeCard"); event = fact for any number of subscribers ("PaymentCaptured") |
| Delivery guarantee | Brokers give at-most-once or at-least-once to consumers. "Exactly-once" end to end requires idempotent consumers or transactional read-process-write inside one system (Kafka transactions) |
Broker Choice
| Need | Kafka | RabbitMQ |
|---|---|---|
| Replay history / new consumers reading the past | Yes (retention-based log) | No by default (queues delete on ack); RabbitMQ Streams add a log |
| Per-key ordering at scale | Yes, per partition | Per queue, single active consumer needed for strict order |
| Flexible routing (topic/headers patterns) | Limited (topic per event type) | Rich (direct, topic, fanout, headers exchanges) |
| Per-message TTL, priority, delayed retry | Not native | Native (TTL, priority queues, DLX) |
| Very high throughput fan-out | Strong | Good, lower ceiling |
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.
- today Changed · +156 lines · +143 tokens per session 282e658dfc33
- 1mo ago First seen · 43 lines · 18 tokens per session scan A 849ecd3ea98d
backend-event-driven-architecture is a skill published in the GitHub repository j4flmao/agent-skills (34 stars, last pushed today), licensed MIT. It adds 161 tokens to every session and 2,249 once invoked, about $0.0006 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 skills, from other repositories
kafka-expert
Expert-level Apache Kafka, event streaming, Kafka Streams, and distributed messaging. Use when the user mentions streaming, messaging, event driven, or Kafka Streams.
event-driven-architecture
Event-driven architecture patterns with event sourcing, CQRS, and message-driven communication. Use when designing distributed systems, microservices communication, or systems requiring eventual consistency and scalability.
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…
Kafka Event-Driven Testing
Test Kafka-based event-driven systems, producer and consumer integration tests with Testcontainers, schema compatibility gates, idempotency and ordering verification, dead-letter handling, and end-to-end event flow assertions.
huawei-cloud-smn-dms-message
Manage Huawei Cloud SMN (Simple Message Notification) topics, subscriptions, message templates and message publishing, and manage DMS (Distributed Message Service) Kafka/RabbitMQ/RocketMQ instances and Kafka topics. 15 built-in actions cover query (list topics/subscriptions/message templates/DMS instances/Kafka…
huawei-cloud-smn-dms-message
Manage Huawei Cloud SMN (Simple Message Notification) topics, subscriptions, message templates and message publishing, and manage DMS (Distributed Message Service) Kafka/RabbitMQ/RocketMQ instances and Kafka topics. 15 built-in actions cover query (list topics/subscriptions/message templates/DMS instances/Kafka…