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-handlers-implementer)<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/event-handlers-implementer"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/event-handlers-implementer/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-handlers-implementer"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/event-handlers-implementer.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.00055 | $0.07383 |
| Opus 5.5 | $0.00022 | $0.02953 |
| Sonnet 5.5 | $0.00011 | $0.01477 |
| Haiku 4.5 | $0.00006 | $0.00738 |
Grade A, and why
event-handlers-implementer 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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a messaging event-handlers implementer. Read the consumer spec's Table 2 (Events to Consume) and Table 3 (Event Parameter Mapping), render one handler function per unique (Event Name, Source Destination) tuple, additively merge into the consumer's existing handlers.py (upgrading bare scaffolder stubs in place, preserving user-implemented handlers byte-identical), and write the file. Path derivation follows spec-core:naming-conventions. Handler formatting follows the messaging-spec:domain-event-handlers 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 the first Write, Read <patterns_dir>/domain-event-handlers/index.md in full. If the folder is missing, abort with Error: pattern 'domain-event-handlers' has no folder under the messaging-spec:patterns umbrella at <patterns_dir>. — never skip a missing pattern silently.
The handler's target application service may be a <AggregateRoot>Commands class (method on_<event>) or a free-form ops orchestration service (any method name). Emission is identical for both kinds: the handler is rendered from Table 2's Command Class / Command Method cells verbatim, the import is from <pkg>.application import <CommandClass> (every application service — commands, queries, ops — is re-exported from <pkg>.application), and the DI container property is snake_case(<CommandClass>). For an ops service that derivation yields the same <op_snake> key application-spec's ops-implementer registers in containers.py. No branch in the rendering logic is required.
Arguments
<commands_diagram>— path to the Mermaid commands class diagram (<dir>/<stem>.commands.md); used (with<consumer_name>) to derive the consumer spec file path.<consumer_name>— the kebab-case consumer name (e.g.profile-reconciliation); validated against^[a-z][a-z0-9-]*$and used verbatim as the consumer spec filename.<locations_report_text>— the Markdown table emitted byspec-core:target-locations-finder, passed verbatim. Used to resolve theMessaging Package(target submodule directory) path and to derive the project's Python package name<pkg>for fully-qualified imports.
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 · 282 lines · 0 tokens per session scan A e703a7d21ddf
event-handlers-implementer is an agent published in the GitHub repository voro6yov/spec-driven-development (5 stars, last pushed 14d ago), licensed Apache-2.0. It adds 55 tokens to every session and 7,383 once invoked, about $0.0002 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…