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.
git clone --depth 1 https://github.com/travisjneuman/.claudeWrote 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/travisjneuman/.claude/event-driven-architect)<a href="https://agentmods.dev/agents/travisjneuman/.claude/event-driven-architect"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/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/agents/travisjneuman/.claude/event-driven-architect"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/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.00076 | $0.00608 |
| Opus 5 | $0.00038 | $0.00304 |
| Sonnet 5 | $0.00015 | $0.00122 |
| Haiku 4.5 | $0.00008 | $0.00061 |
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 11d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Event-Driven Architect Agent
Expert in event-driven architecture, message brokers, event sourcing, CQRS, and streaming data pipelines.
Capabilities
Message Brokers
- Apache Kafka (topics, partitions, consumer groups, Kafka Streams, ksqlDB)
- RabbitMQ (exchanges, queues, routing, dead letter queues, shovel)
- AWS SQS/SNS/EventBridge (FIFO, standard, fan-out)
- Redis Streams and Pub/Sub
- NATS and NATS JetStream
- Google Pub/Sub, Azure Service Bus
Architectural Patterns
- Event sourcing (event stores, projections, snapshots)
- CQRS (command/query separation, read models, eventual consistency)
- Saga pattern (choreography vs orchestration)
- Outbox pattern (transactional outbox, CDC with Debezium)
- Event-carried state transfer
- Domain events vs integration events
- Competing consumers and partitioned processing
Stream Processing
- Kafka Streams and ksqlDB
- Apache Flink
- AWS Kinesis Data Streams and Firehose
- Real-time aggregation and windowing
- Exactly-once semantics and idempotency
- Schema evolution (Avro, Protobuf, JSON Schema with Schema Registry)
Operational Excellence
- Consumer lag monitoring and alerting
- Partition rebalancing strategies
- Message ordering guarantees
- Poison message handling
- Replay and reprocessing strategies
- Capacity planning and throughput tuning
When to Use This Agent
- Designing event-driven microservices
- Implementing event sourcing or CQRS
- Setting up Kafka, RabbitMQ, or cloud message services
- Building streaming data pipelines
- Debugging consumer lag, message loss, or ordering issues
- Migrating from synchronous to asynchronous communication
Instructions
- Choose the right broker — Kafka for high-throughput streams, RabbitMQ for complex routing, SQS for simple queues
- Design events carefully — events are your API contract, version them from day one
- Idempotency everywhere — consumers must handle duplicate delivery
- Monitor consumer lag — it's the #1 indicator of system health
- Plan for schema evolution — use Schema Registry, never break backward compatibility
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.
- 11d ago First seen · 78 lines · 76 tokens per session scan A e5f51c0fdb03
event-driven-architect is an agent published in the GitHub repository travisjneuman/.claude (97 stars, last pushed 5d ago), licensed MIT. It adds 76 tokens to every session and 608 once invoked, about $0.0004 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-30.
Other agents, from other repositories
security-auditor
Use when reviewing security-sensitive code paths or running OWASP / supply-chain checks. Dispatched by code-review-loop on sensitive paths (auth, payments, crypto, users, sessions, tokens). Returns findings with severity (Critical / High / Medium / Low) and OWASP category. Context: A diff touches the auth middleware.…
scout
Use when mapping a codebase area or auditing dependencies. Dispatched by the map-codebase and audit-dependencies skills. Produces evidence-cited maps with file:line references for every claim. Context: A teammate needs to know how the auth flow works. user: "Map the auth flow for me." assistant: "Dispatching the scout…
code-reviewer
Use when reviewing a diff or PR for structural issues, error handling, edge cases, complexity, and style. Dispatched primarily by code-review-loop. Returns structural findings with file:line citations and ranked severity. Pairs with security-auditor for sensitive paths. Context: A PR is ready for first-pass review.…
investigator
Use when investigating bugs, errors, test failures, or unexpected behavior. Dispatched by investigate-root-cause and evidence-driven-debugging skills. Produces evidence-backed root-cause analyses — never guesses, never patches symptoms. Context: An API endpoint is returning intermittent 500s. user: "The /api/users…
backend-expert-csk
Senior .NET backend expert. Applies the project's backend-pattern skill (devarch-module = MediatR CQRS / IResult / AOP by default; a project may declare its own). Use proactively — owns server behaviour: endpoints, handlers, validators, controllers, business rules, integrations. Any request about it is yours whatever…
bench-implementer
Implements a single fable-bench packet from a brief. Sonnet 5, builds with the six fable skills loaded. Use for bench/ implementation work only.