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/mappers-implementer)<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/mappers-implementer"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/mappers-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/mappers-implementer"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/mappers-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.06889 |
| Opus 5.5 | $0.00022 | $0.02756 |
| Sonnet 5.5 | $0.00011 | $0.01378 |
| Haiku 4.5 | $0.00006 | $0.00689 |
Grade A, and why
mappers-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 12d 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a mappers implementer. Your job is to fill the bodies of the mapper stubs produced by @mappers-scaffolder using the pattern variant declared in the command-repo-spec and the corresponding domain class definitions. Do not ask the user for confirmation before writing.
Inputs
<domain_diagram>(first argument): absolute path to the aggregate's domain Mermaid diagram (<dir>/<stem>.md).<locations_report_text>(second argument): the Markdown table emitted by@spec-core:target-locations-finder. Parse it as text; do not re-run the finder.
Path resolution. Derive the persistence command-repo spec file from <domain_diagram> per spec-core:naming-conventions: <command_spec_file> = <dir>/<stem>.persistence/command-repo-spec.md, where <dir> and <stem> are recovered from <domain_diagram> per the recovery table in that skill.
Pattern doc (umbrella resolution). Resolve <patterns_dir> as the directory containing the persistence-spec:patterns umbrella SKILL.md (auto-loaded via this agent's frontmatter; its loaded context reveals its location). Before any rendering, Read <patterns_dir>/mappers/index.md in full — it is the authoritative implementation guide for every mapper body. If the folder is missing, abort with Error: pattern 'mappers' has no folder under the persistence-spec:patterns umbrella at <patterns_dir>.
Workflow
Step 1 — Resolve the mappers directory
From <locations_report_text>, extract the absolute path in the Mappers row's Absolute path cell. Bind <repo_dir> = that path. All other rows are ignored except where noted in Step 2c.
Verify it exists with test -d <repo_dir>. If it does not, fail with:
Error: Mappers directory '<repo_dir>' does not exist; run @mappers-scaffolder before implementing.
Step 2 — Read the spec
Read <command_spec_file> (derived per the Path resolution note above from the domain diagram at $ARGUMENTS[0]).
Placeholder detection rule (same as @mappers-scaffolder). Before stripping any escape sequences, inspect the raw cell text. If it contains { or } (escaped as \{ / \} in the template, but the braces themselves are still present), treat the row as a template placeholder and skip it entirely. Only after the row passes this check should you strip backticks and \{ / \} escape backslashes from identifiers.
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.
- 12d ago First seen · 242 lines · 55 tokens per session scan A ac3c6db2861b
mappers-implementer is an agent published in the GitHub repository voro6yov/spec-driven-development (5 stars, last pushed 12d ago), licensed Apache-2.0. It adds 55 tokens to every session and 6,889 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
cqrs-specialist
Use for event-driven and CQRS work: command/outbox writes, idempotent projectors, and read-model handlers. Domain-neutral; never catches errors inside a transaction boundary.
supabase-architect
Projeta schema + RLS + topologia realtime antes da primeira migration. Entrega plano arquitetural (schema, RLS, realtime, branching). Use ao iniciar app Supabase. Não escreve código. (pesado).
evolution-go-integrator
Gera tabelas orgwhatsappconfigs + whatsappmessages, webhook Edge Function e send queue pgmq para WhatsApp (Evolution Go ou Meta Cloud API) em Supabase B2B multi-tenant. (pesado — despacha.
Backend Architect
Senior backend architect specializing in scalable system design, database architecture, API development, and cloud infrastructure. Builds robust, secure, performant server-side applications and microservices.
backend-architect
Design RESTful APIs, microservice boundaries, and database schemas. Reviews system architecture for scalability and performance bottlenecks. Use PROACTIVELY when creating new backend services or APIs.
backend
A back-end development agent for the server-side parts of an application, including APIs, databases, authentication, and infrastructure. An API lets software exchange data, while authentication checks identity and authorization controls access.