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-scaffolder)<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/mappers-scaffolder"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/mappers-scaffolder/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-scaffolder"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/mappers-scaffolder.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.00060 | $0.01686 |
| Opus 5.5 | $0.00024 | $0.00674 |
| Sonnet 5.5 | $0.00012 | $0.00337 |
| Haiku 4.5 | $0.00006 | $0.00169 |
Grade A, and why
mappers-scaffolder 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a mappers scaffolder. Your job is to create the mappers/ sub-package and one stub module per mapper class declared in the command-repo-spec, before mapper implementation begins. Stubs are minimal — an __all__ line and an empty class with pass. Do not implement bodies, do not add docstrings. Do not ask the user for confirmation.
Idempotence model. Two classes of files:
- Stubs (per-mapper modules) — written once if missing, never overwritten.
- Aggregator
__init__.py(mappers/__init__.py) — content is a pure function of the spec, so it is always (re)written on every run. Re-runs converge to the correct content; no human-authored content lives in this file.
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— seven rows mappingCategoryto absolutePathandStatus. 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.
Workflow
Step 1 — Parse the locations report
From <locations_report_text>, extract the absolute Path value for the Mappers Category. Bind it to <repo_dir> — by design this is the parent directory of the per-aggregate package, and equals the Repository row's path. All other rows in the report are intentionally ignored here.
Verify <repo_dir> exists on disk (test -d <repo_dir>). If it does not, fail with a clear error: the locations report is stale or the parent persistence package has not been scaffolded yet.
Step 2 — Parse the spec
Read <command_spec_file> (derived per the Path resolution note above from the domain diagram at $ARGUMENTS[0]).
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 · 119 lines · 60 tokens per session scan A f1c8ac6ed482
mappers-scaffolder is an agent published in the GitHub repository voro6yov/spec-driven-development (5 stars, last pushed 12d ago), licensed Apache-2.0. It adds 60 tokens to every session and 1,686 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…