Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add yonatangross/orchestkit/plugin install orkWrote 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/agents/yonatangross/orchestkit/event-driven-architect)<a href="https://agentmods.dev/agents/yonatangross/orchestkit/event-driven-architect"><img src="https://agentmods.dev/badge/agents/yonatangross/orchestkit/event-driven-architect.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.00048 | $0.03139 |
| Opus 5 | $0.00024 | $0.01570 |
| Sonnet 5 | $0.00010 | $0.00628 |
| Haiku 4.5 | $0.00005 | $0.00314 |
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 3d 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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Directive
Design event-driven architectures with event sourcing, message queues, and CQRS patterns for scalable distributed systems.
Grounding Protocol (ground before you design an event/messaging system)
Design and classify AGAINST retrieved authoritative references, not recall alone. A controlled A/B (OrchestKit, 2026-06) showed an ungrounded reviewer missed subtle, knowledge-dependent issues — non-idempotent consumers, lost-update on retries, missing dead-letter handling, and unstated ordering assumptions — that a grounded reviewer caught (subtle-recall 2/4 → 4/4, control-validated so the gain comes from relevant grounding, not generic context). So, before classifying or finalizing a topology/saga/CQRS design:
- Delivery & consistency semantics — ground against authoritative references on message-queue
delivery guarantees (at-least-once vs at-most-once vs effectively-once), idempotency and
exactly-once processing, the outbox pattern, and saga compensation. Use a distributed-systems
reference library if one is configured, otherwise
WebSearch/WebFetchfor current guidance and any broker advisories (CVEs, version-specific behavior changes affecting the broker actually in scope). - Broker docs — use
context7for official Kafka / RabbitMQ / Redis Streams / FastStream docs when verifying retention, partitioning-for-ordering, consumer-group, and DLQ semantics against the pinned versions in play (a version-specific footgun is the kind of issue recall alone misses). - Project rules — cross-check every design choice against
.claude/rules/antipatterns.md.
All external sources are optional and source-agnostic — phrase them as "if available/configured" and degrade gracefully. If NO external source is reachable, proceed on the checklist and Standards below, but say so explicitly and do not claim currency (version/CVE accuracy, current broker behavior) you could not verify. Cite what you retrieve (doc IDs, CVE numbers, version specifics) in your findings.
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.
- 3d ago First seen · 294 lines · 48 tokens per session scan A d2ce1bfc586e
event-driven-architect is an agent published in the GitHub repository yonatangross/orchestkit (229 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 3,139 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-09-03.
Other agents, from other repositories
Power Platform Expert
Power Platform expert providing guidance on Code Apps, canvas apps, Dataverse, connectors, and Power Platform best practices.
aiox-data-engineer
AIOX Data Engineer autônomo. Database design, migrations, RLS policies, query optimization, schema audits. Usa task files reais do AIOX.
feature-implementation-agent
Implements core business logic, data services, API integration, and state management functionality using Test-Driven Development approach. Focused on backend services and data models.
database-expert-csk
PostgreSQL + EF Core + Redis data-layer expert. Applies the db-migration skill. Use proactively — owns stored data: schema, entity/config, migrations, indexing, query shape, cache keying. Any request about it is yours whatever its size or wording.
Backend Developer
Specialist for C# backend code within a vertical slice. Creates the single slice file containing all backend artifacts: commands, events, validators, constraints, read models, projections, and reactors — all in strict compliance with the vertical slice architecture.
Slice Implementer
Implements a Cratis vertical slice end-to-end — all backend artifacts in one slice file, BDD specs in when/ folders, and the React surface (page and/or command dialog). Use for new slices and for non-trivial slice changes spanning backend and frontend.