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 Tyler-R-Kendrick/agent-skills --skill event-drivengit clone --depth 1 https://github.com/Tyler-R-Kendrick/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/tyler-r-kendrick/agent-skills/event-driven)<a href="https://agentmods.dev/skills/tyler-r-kendrick/agent-skills/event-driven"><img src="https://agentmods.dev/badge/skills/tyler-r-kendrick/agent-skills/event-driven/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/tyler-r-kendrick/agent-skills/event-driven"><img src="https://agentmods.dev/badge/skills/tyler-r-kendrick/agent-skills/event-driven.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.00100 | $0.03312 |
| Opus 5 | $0.00050 | $0.01656 |
| Sonnet 5 | $0.00020 | $0.00662 |
| Haiku 4.5 | $0.00010 | $0.00331 |
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 10d 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Event-Driven Architecture, Event Sourcing & CQRS
Overview
This skill covers three complementary but independent patterns that are frequently used together:
- Event-Driven Architecture (EDA) -- A system design where components communicate through events rather than direct calls.
- Event Sourcing -- A persistence pattern where state is stored as a sequence of events rather than as current state.
- CQRS (Command Query Responsibility Segregation) -- A pattern that separates read and write models.
These patterns can be used independently or combined. Understanding when to use each -- and when to combine them -- is critical.
Canonical Works
| Book | Author(s) | Relevant Coverage |
|---|---|---|
| Designing Data-Intensive Applications | Martin Kleppmann | Event sourcing, stream processing, change data capture |
| Implementing Domain-Driven Design | Vaughn Vernon | Domain events, event sourcing with DDD, CQRS |
| Building Event-Driven Microservices | Adam Bellemare | EDA at scale, event mesh, stream processing |
| Enterprise Integration Patterns | Hohpe & Woolf | Messaging foundations (see dev/integration-patterns) |
Relationship Between the Three Patterns
┌─────────────────────────────────────────────────────────┐
│ │
│ Event-Driven Architecture (EDA) │
│ Components communicate through events │
│ │
│ ┌──────────────────┐ ┌──────────────────┐ │
│ │ Event Sourcing │ │ CQRS │ │
│ │ Store state as │ │ Separate read │ │
│ │ event log │ │ and write models │ │
│ └────────┬─────────┘ └────────┬─────────┘ │
│ │ │ │
│ └───────────┬───────────┘ │
│ │ │
│ Can be combined but │
│ are independent patterns │
│ │
└─────────────────────────────────────────────────────────┘
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- AGENTS.md 15 KB
- metadata.json 846 B
- README.md 664 B
- rules/_sections.md 1.8 KB
- rules/_template.md 371 B
- rules/event-driven-build-projections-to-be-rebuildable.md 359 B
- rules/event-driven-design-events-as-first-class-domain-concepts.md 374 B
- rules/event-driven-handle-idempotency-in-all-event-consumers.md 330 B
- rules/event-driven-keep-the-write-model-focused-on-enforcing-business.md 388 B
- rules/event-driven-monitor-projection-lag-time-between-event-publication-and.md 398 B
- rules/event-driven-plan-for-event-schema-evolution-from-day-one.md 364 B
- rules/event-driven-start-with-eda-alone-if-you-only-need-loose-coupling-and.md 426 B
- rules/event-driven-use-snapshots-for-long-lived-event-streams-to-keep-replay.md 365 B
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.
- 10d ago First seen · 287 lines · 100 tokens per session scan A 855aa5ed6ac7
event-driven is a skill published in the GitHub repository Tyler-R-Kendrick/agent-skills (11 stars, last pushed 3mo ago), licensed MIT. It adds 100 tokens to every session and 3,312 once invoked, about $0.0005 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
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
convex-explain-app
Explain an existing Convex app — data model + relationships, public vs internal functions, auth/ownership model, components, a request→data flow — read from the schema and function surface. Read-only.
platform-custom-field-generate
Use this skill when users need to create, generate, or validate Salesforce Custom Field metadata. Trigger when users mention custom fields, field types, Roll-up Summary fields, Master-Detail relationships, Lookup relationships, formula fields, picklists, dependent (controlling) picklists, referencing a value set from…
field-service-sobject-create-configure
Headless 360 REST API deployment step for creating sObject records. Handles describe-based field discovery, required-field derivation, entity-relationship ordering, and composite graph transactions. Use this skill when a designer skill (or a user directly) needs to create sObject records after design confirmation…
durable-objects
Build, debug, or review Cloudflare Durable Objects code for persistent state and coordination.
nornicdb-grpc
Drive NornicDB over gRPC — the Qdrant-compatible surface (Collections, Points, Snapshots) plus the additive NornicSearch service. Use when ingesting via Qdrant SDKs, migrating from Qdrant, or running hybrid text+vector search from a non-Bolt client. Covers connection, RPC catalog, collection→database mapping…