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 Plazmodium/odin-workflow --skill event-drivengit clone --depth 1 https://github.com/Plazmodium/odin-workflowWrote 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/plazmodium/odin-workflow/event-driven)<a href="https://agentmods.dev/skills/plazmodium/odin-workflow/event-driven"><img src="https://agentmods.dev/badge/skills/plazmodium/odin-workflow/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/plazmodium/odin-workflow/event-driven"><img src="https://agentmods.dev/badge/skills/plazmodium/odin-workflow/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.00020 | $0.01055 |
| Opus 5.5 | $0.00008 | $0.00422 |
| Sonnet 5.5 | $0.00004 | $0.00211 |
| Haiku 4.5 | $0.00002 | $0.00105 |
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 1mo 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Event-Driven Architecture
Overview
Event-driven architecture (EDA) uses events as the primary mechanism for communication between components. Events represent facts — things that have happened — and enable loose coupling, scalability, and auditability.
Patterns
Event Notification
Producer → Event Bus → Consumer(s)
OrderService NotificationService
│ │
├── publishes ──► OrderPlaced ──► │ sends email
│ │
InventoryService PaymentService
│ │
├── subscribes ─► OrderPlaced ──► │ charges card
Event Sourcing
// Store events, not state — rebuild state by replaying events
class OrderEventStore {
async save(orderId: string, events: DomainEvent[]): Promise<void> {
for (const event of events) {
await this.db.insert('events', {
stream_id: orderId,
type: event.type,
data: JSON.stringify(event),
version: event.version,
occurred_at: event.occurredAt,
});
}
}
async load(orderId: string): Promise<DomainEvent[]> {
return this.db.query(
'SELECT * FROM events WHERE stream_id = $1 ORDER BY version ASC',
[orderId]
);
}
}
// Rebuild aggregate from events
function rehydrate(events: DomainEvent[]): Order {
const order = new Order();
for (const event of events) {
order.apply(event); // Mutates internal state
}
return order;
}
CQRS (Command Query Responsibility Segregation)
Commands (Write) Queries (Read)
│ │
▼ ▼
┌──────────┐ events ┌──────────────────┐
│ Write DB │ ──────────► │ Read Projections │
│ (events) │ │ (denormalized) │
└──────────┘ └──────────────────┘
// Command side — validates and stores events
async function placeOrder(cmd: PlaceOrderCommand): Promise<void> {
const order = await eventStore.load(cmd.orderId);
const events = order.place(cmd.items); // Returns new events
await eventStore.save(cmd.orderId, events);
await eventBus.publish(events);
}
// Query side — read from optimized projections
async function getOrderSummary(orderId: string): Promise<OrderSummary> {
return readDb.query('SELECT * FROM order_summaries WHERE id = $1', [orderId]);
}
// Projector — updates read model when events arrive
class OrderProjector {
async handle(event: OrderPlaced): Promise<void> {
await readDb.insert('order_summaries', {
id: event.orderId,
status: 'placed',
total: event.total,
item_count: event.items.length,
});
}
}
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.
- 1mo ago First seen · 146 lines · 20 tokens per session scan A cdd23109217e
event-driven is a skill published in the GitHub repository Plazmodium/odin-workflow (0 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 1,055 once invoked, about $0.0001 per session on Opus 5.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-01.
Other skills, from other repositories
frontmcp-guides
Tutorials, end-to-end walkthroughs, and complete reference projects for FrontMCP. Use when you want a getting-started guide, a full worked example, or to learn best practices by following a step-by-step build rather than a single API reference. Includes a beginner weather-API server (tool plus static resource, Zod…
nornweave-api
Give AI agents their own email inboxes using the NornWeave API. Use when building email agents, sending/receiving emails programmatically, managing inboxes, retrieving threads, searching messages, or integrating with email providers (Mailgun, SES, SendGrid, Resend). NornWeave provides LLM-ready markdown parsing and…
user-usecases
Database of real user use cases for APIbase platform. Contains detailed examples of how specific APIs are onboarded, wrapped, and served to AI agents. Use this skill when you need to reference real integration examples, explain the APIbase onboarding process, or design new API wrappers based on proven patterns.
golang-manual-di
Guides manual dependency injection wiring for Go services: three-tier naming taxonomy (Provide/MustProvide/Must), Must-pattern entrypoints, OS-signal-driven context lifecycle, common provider structs, infrastructure must-builders, interface-segregated bus registration, decorator/tracing wrappers, and…
terraform-infrastructure
Structures, writes, and reviews Terraform infrastructure code. Covers module layout, remote state, workspace strategy, variable and secrets handling, CI plan/apply pipeline, naming conventions, and multi-region deployment patterns (provider aliases, per-region state, failover strategies), while delegating shared risk…
microservices-architecture
Guides service boundary analysis, communication pattern selection, data consistency design, API contract strategy, and resilience checklist for microservices systems. Complements the microservices fragment. Invoked when the user asks to design a microservices system, split a monolith, or review service boundaries.