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 martineserios/thebrana --skill event-driven-architectgit clone --depth 1 https://github.com/martineserios/thebranaWrote 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/martineserios/thebrana/event-driven-architect)<a href="https://agentmods.dev/skills/martineserios/thebrana/event-driven-architect"><img src="https://agentmods.dev/badge/skills/martineserios/thebrana/event-driven-architect/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/martineserios/thebrana/event-driven-architect"><img src="https://agentmods.dev/badge/skills/martineserios/thebrana/event-driven-architect.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.00052 | $0.01628 |
| Opus 5 | $0.00026 | $0.00814 |
| Sonnet 5 | $0.00010 | $0.00326 |
| Haiku 4.5 | $0.00005 | $0.00163 |
Grade A, and why
event-driven-architect 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 9d 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.
This is a copy
88% identical to event-driven-architect — 27 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Event-Driven Architect
Design asynchronous systems built around durable events, explicit contracts, and operationally safe consumers.
Scope: Event-driven application architecture and reliability patterns. NOT for synchronous API design (api-designer) or batch ETL pipeline design (data-pipeline-architect).
Canonical Vocabulary
| Term | Definition |
|---|---|
| event | Immutable record of something that happened |
| command | Request to perform an action, not a fact |
| topic | Named stream or channel carrying related events |
| partition key | Value used to preserve order for a subset of events |
| consumer group | Independent set of workers processing the same topic |
| idempotency key | Stable identity used to make repeated processing safe |
| dead-letter queue | Holding area for messages that exceeded normal retries |
| outbox | Transactional pattern for publishing events from database changes |
| saga | Multi-step workflow coordinated through events and compensations |
| contract version | Compatibility marker for event schema evolution |
Dispatch
| $ARGUMENTS | Mode |
|---|---|
design <domain or workflow> |
Design an event-driven architecture |
review <architecture or code path> |
Audit an existing event flow |
contract <event> |
Define or evolve an event contract |
reliability <flow> |
Design retries, ordering, and recovery |
migration <change> |
Plan adoption or replacement of an event flow |
| Natural language about queues, brokers, or async workflows | Auto-detect the closest mode |
| Empty | Show the mode menu with examples |
Mode Menu
| # | Mode | Example |
|---|---|---|
| 1 | Design | design order fulfillment across payments, inventory, and shipping |
| 2 | Review | review event flow for user-created -> email sync |
| 3 | Contract | contract invoice.paid |
| 4 | Reliability | reliability retry strategy for webhook ingestion |
| 5 | Migration | migration move monolith side effects to events |
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.
- 9d ago First seen · 150 lines · 52 tokens per session scan A 81a2f4fb6363
event-driven-architect is a skill published in the GitHub repository martineserios/thebrana (3 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 1,628 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to event-driven-architect, differing in 27 lines, and is treated as a copy.
Other skills, from other repositories
event-driven
Event-driven architecture authority — Redis pub/sub, event bus patterns, async event pipelines, channel management, startup recovery, dead-letter handling, and reactive system design.
python-backend
Production Python async patterns including asyncio TaskGroup, FastAPI dependency injection and middleware, SQLAlchemy 2.0 async sessions, and database connection pool tuning. Python 3.11+ runtime concerns such as ExceptionGroup, cancellation semantics, and session rollback. Use when building async services, wiring…
async-jobs
Async job processing patterns for background tasks, Celery workflows, task scheduling, retry strategies, and distributed task execution. Use when implementing background job processing, task queues, or scheduled task systems.
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.
backend-transactional-outbox
Use this skill when the user says 'outbox', 'transactional outbox', 'outbox pattern', 'reliable event publishing', 'dual write', 'CDC outbox', 'message relay', 'publish events reliably', 'exactly-once publish', 'debezium outbox'. This skill enforces: event publication in the same DB transaction as business data…
Event-Driven Semantics & Delivery Guarantees
Ensure event-driven designs specify delivery guarantees, ordering, idempotency, schema evolution, and replay/backfill strategy.