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 khalilbenaz/claude-skills-collection --skill event-driven-architectgit clone --depth 1 https://github.com/khalilbenaz/claude-skills-collectionWrote 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/khalilbenaz/claude-skills-collection/event-driven-architect)<a href="https://agentmods.dev/skills/khalilbenaz/claude-skills-collection/event-driven-architect"><img src="https://agentmods.dev/badge/skills/khalilbenaz/claude-skills-collection/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/khalilbenaz/claude-skills-collection/event-driven-architect"><img src="https://agentmods.dev/badge/skills/khalilbenaz/claude-skills-collection/event-driven-architect.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.00143 | $0.02174 |
| Opus 5 | $0.00072 | $0.01087 |
| Sonnet 5 | $0.00029 | $0.00435 |
| Haiku 4.5 | $0.00014 | $0.00217 |
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.
How it starts
The opening of the file, as written. The whole thing — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Event-Driven Architect
Workflow
1. Identifier les événements métier
Modéliser les faits immuables nommés au passé (verbe passé + sujet) :
OrderPlaced / PaymentProcessed / UserRegistered / ShipmentDispatched
Distinguer deux types :
- Domain event : interne à un bounded context (même déploiement possible).
- Integration event : traverse les frontières de service → passe obligatoirement par un broker.
Pratiquer l'Event Storming pour découvrir les événements avec les parties métier avant d'écrire la moindre ligne de code.
2. Choisir le broker
| Critère | RabbitMQ | Kafka | Azure Service Bus | Redis Streams |
|---|---|---|---|---|
| Débit | Moyen (50 k msg/s) | Très élevé (M msg/s) | Moyen | Faible-moyen |
| Rétention | Non (ack = supprimé) | Oui (configurable) | 14 jours max | Configurable |
| Ordering strict | Par queue | Par partition | Par session | Par stream |
| Rejeu | Non natif | Oui | Non natif | Oui |
| Complexité opé. | Faible | Élevée | Faible (SaaS) | Très faible |
Règle de sélection :
- Audit trail / event sourcing / gros débit → Kafka
- Workflow, saga, routing complexe → RabbitMQ
- Équipe Azure sans infra dédiée → Azure Service Bus
- Cache + messaging léger → Redis Streams
3. Topologie topics / queues
RabbitMQ — exchange fanout + routing :
Exchange: order.events (type: topic)
→ order.placed → queue: billing.order-placed
→ order.placed → queue: inventory.order-placed
→ order.cancelled → queue: billing.order-cancelled
Kafka — topics + partitions :
Topic: order-events (partitions: 12, replication: 3)
Topic: payment-events (partitions: 6, replication: 3)
Consumer group: billing-svc → offset par partition géré par Kafka
Règle : 1 consumer group = 1 responsabilité. Ne pas partager un group entre services différents.
4. Implémenter le pattern
Pub/Sub (découplage simple)
// Producteur (.NET + MassTransit + RabbitMQ)
await _publishEndpoint.Publish(new OrderPlaced
{
OrderId = order.Id,
CustomerId = order.CustomerId,
OccurredAt = DateTimeOffset.UtcNow
});
// Consommateur
public class OrderPlacedConsumer : IConsumer<OrderPlaced>
{
public async Task Consume(ConsumeContext<OrderPlaced> context)
{
// logique idempotente ici
}
}
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 · 261 lines · 143 tokens per session scan A 31c55c72f182
event-driven-architect is a skill published in the GitHub repository khalilbenaz/claude-skills-collection (22 stars, last pushed 19d ago), licensed MIT. It adds 143 tokens to every session and 2,174 once invoked, about $0.0007 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 skills, from other repositories
api-patterns
API design: naming, versioning, pagination, idempotency, OpenAPI, error contracts and safe retries. Triggers: API design, REST, GraphQL, OpenAPI, Swagger, error response, HTTP status, rate limit.
csharp-patterns
C#/.NET: LINQ, async/await, DI, records, nullable refs, ASP.NET Core, EF Core, MediatR. Triggers: C#, .NET, dotnet, ASP.NET, EF Core, LINQ, record type, IServiceCollection.
java-patterns
Java: Spring Boot, CompletableFuture, records, sealed types, JPA/Hibernate, virtual threads. Triggers: Java, Spring, JPA, Hibernate, Maven, Gradle, virtual thread, sealed class.
medplum-rules
Medplum (FHIR healthcare) coding rules: style, patterns, security, testing. Triggers: medplum.config.mts, medplum.config.ts, FHIR, Medplum, Bot, Subscription, Questionnaire.
api-design
REST API contract designer and reviewer. ALWAYS use when designing new endpoints, reviewing existing API contracts, planning API versioning, or standardizing error models. Covers resource modeling (URL/naming), HTTP method semantics, status code selection, error model consistency, pagination/filtering/sorting…
kafka-event-driven-design
Kafka event-driven architecture designer and reviewer, at the application/client layer. ALWAYS use when designing, reviewing, or troubleshooting how a service produces or consumes Kafka events — topic and partition-key design, producer and consumer client configuration, consumer group topology, event schema definition…