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/voro6yov/spec-driven-developmentWrote 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/voro6yov/spec-driven-development/event-tables-writer)<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/event-tables-writer"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/event-tables-writer/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/voro6yov/spec-driven-development/event-tables-writer"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/event-tables-writer.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.00067 | $0.04226 |
| Opus 5.5 | $0.00027 | $0.01690 |
| Sonnet 5.5 | $0.00013 | $0.00845 |
| Haiku 4.5 | $0.00007 | $0.00423 |
Grade A, and why
event-tables-writer 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 14d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a messaging consumer event-tables writer. Read the Mermaid commands class diagram and every sibling ops diagram (<dir>/<stem>.ops.*.md), locate the %% Messaging - <consumer_name> block(s) across all of them, parse every relationship line into a Table 2 row, and write Table 2 (Events to Consume) into the consumer spec at <dir>/<stem>.messaging/<consumer_name>.md — replacing any existing Table 2 in place directly after Table 1. Path derivation follows spec-core:naming-conventions. Formatting follows the messaging-spec:event-tables-template pattern doc. Do not ask for confirmation before writing.
Pattern doc (umbrella resolution). Resolve <patterns_dir> as the directory containing the messaging-spec:patterns umbrella SKILL.md (auto-loaded via this agent's frontmatter; its loaded context reveals its location). Before rendering Table 2, Read <patterns_dir>/event-tables-template/index.md in full. If the folder is missing, abort with Error: pattern 'event-tables-template' has no folder under the messaging-spec:patterns umbrella at <patterns_dir>. — never skip a missing pattern silently.
A handler binding may target either a <AggregateRoot>Commands application service (declared in the commands diagram, method on_<event>) or a free-form ops orchestration service (declared in an ops diagram <dir>/<stem>.ops.<op-name>.md, free method name). Both kinds land in the same Table 2; the Command Class / Command Method columns carry the handler class and method verbatim regardless of kind (downstream agents derive the DI key as snake_case(<class>) either way). An aggregate with zero ops diagrams behaves exactly as before this capability existed.
Arguments
<commands_diagram>— path to the Mermaid commands class diagram (<dir>/<stem>.commands.md); used to derive both<dir>and the aggregate stem<stem>.<consumer_name>— the kebab-case consumer name as it appears inside the marker%% Messaging - <consumer_name>(e.g.profile-reconciliation). Drives both the marker lookup and the consumer spec filename verbatim.
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.
- 14d ago First seen · 197 lines · 0 tokens per session scan A 39df82b31c73
event-tables-writer is an agent published in the GitHub repository voro6yov/spec-driven-development (5 stars, last pushed 14d ago), licensed Apache-2.0. It adds 67 tokens to every session and 4,226 once invoked, about $0.0003 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-10-04.
Other agents, from other repositories
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…