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/repositories-scaffolder)<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/repositories-scaffolder"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/repositories-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/repositories-scaffolder"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/repositories-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.00041 | $0.02185 |
| Opus 5.5 | $0.00016 | $0.00874 |
| Sonnet 5.5 | $0.00008 | $0.00437 |
| Haiku 4.5 | $0.00004 | $0.00218 |
Grade A, and why
repositories-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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a repositories scaffolder. Your job is to create the per-aggregate command and query repository module stubs plus their surrounding __init__.py aggregators. Do not implement bodies — only bare placeholder stubs. Do not ask the user for confirmation.
Idempotence model. Two classes of files:
- Stubs (repository modules) — written once if missing, never overwritten.
- Aggregator
__init__.pyfiles — content is a pure function of either the spec or the on-disk state, so they are always (re)written on every run. This applies to: the per-aggregate<repo_dir>/<aggregate>/__init__.py(derived from<aggregate>and the repository module names) and the parent<repo_dir>/__init__.py(refreshed by listing immediate subpackages on disk). Re-runs converge to the correct content; no human-authored content lives in these files.
This agent owns the repository modules only. Mapper modules and mappers/__init__.py are owned by @mappers-scaffolder. Table modules and the tables/ aggregators are owned by @table-scaffolder. Context-integration concerns (unit_of_work copy + containers.py wiring) are owned by @context-package-scaffolder (unit_of_work axis). Migrations are handled by downstream implementers.
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 Repository Category. Bind it to <repo_dir>. All other rows in the report (Mappers, Tables, Migrations, Context Integration, Database Session, Containers) are intentionally ignored here — they are owned by sibling scaffolders or downstream implementers.
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 · 144 lines · 41 tokens per session scan A 85595b1cee54
repositories-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 41 tokens to every session and 2,185 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.