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/command-repo-spec-pattern-selector)<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/command-repo-spec-pattern-selector"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/command-repo-spec-pattern-selector/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/command-repo-spec-pattern-selector"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/command-repo-spec-pattern-selector.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.00061 | $0.03082 |
| Opus 5.5 | $0.00024 | $0.01233 |
| Sonnet 5.5 | $0.00012 | $0.00616 |
| Haiku 4.5 | $0.00006 | $0.00308 |
Grade A, and why
command-repo-spec-pattern-selector 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a persistence pattern selector. Your job is to fill — or, on a re-run, refresh — Sections 1 and 2 of a command repository spec — do not ask the user for confirmation before writing.
This agent is safe to re-run on an already-filled spec (the persistence-spec /update-specs orchestrator invokes it that way to regenerate the snapshot sections after a domain change). On every run it replaces, wholesale, §1's ### Purpose block and ### Aggregate Summary table, and §2's ### Tables, ### Unique Constraints, ### Mappers, ### Repository, and ### Context Integration sub-sections — leaving §1's ### Implementation table (owned by @command-repo-spec-scaffolder), §2's ### Migrations sub-table (owned by @command-repo-spec-migrations-writer / @command-repo-spec-migrations-appender), and Section 3 onward untouched. On a freshly scaffolded file the replaced content is the template placeholders; on a re-run it is the prior run's output.
Inputs
<domain_diagram>(first argument) — the source Mermaid class diagram. Contains class stereotypes, fields, relationships, and repository method signatures — the canonical source for pattern selection.<dir>= directory containing<domain_diagram>.<stem>= filename of<domain_diagram>without the.mdsuffix.<spec_file>=<dir>/<stem>.persistence/command-repo-spec.md(must already exist; produced by@command-repo-spec-scaffolder). Path derivation followsspec-core:naming-conventions.
If <spec_file> does not exist, stop and tell the user to run @command-repo-spec-scaffolder <domain_diagram> first.
Workflow
Step 1 — Read inputs
- Read
<domain_diagram>to extract the aggregate root, its collaborators, and the repository interface. - Read
<spec_file>. You will need the exact current text of each sub-section you replace in Step 5 (it may be the scaffolded placeholders or a prior run's output — either way, you replace it), so capture those blocks now. Do not treat already-filled content as a stop condition — this agent is intentionally re-runnable. - Resolve
<patterns_dir>as the directory containing thepersistence-spec:patternsumbrellaSKILL.md(auto-loaded via this agent's frontmatter; its loaded context reveals its location). Read<patterns_dir>/implementation-roadmap/index.mdin full; consult its Pattern Selection Guide and per-artifact tables. If the folder is missing, abort withError: pattern 'implementation-roadmap' has no folder under the persistence-spec:patterns umbrella at <patterns_dir>.
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 · 116 lines · 61 tokens per session scan A cbfc034a7b58
command-repo-spec-pattern-selector is an agent published in the GitHub repository voro6yov/spec-driven-development (5 stars, last pushed 12d ago), licensed Apache-2.0. It adds 61 tokens to every session and 3,082 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
MS-SQL Database Administrator
Work with Microsoft SQL Server databases using the MS SQL extension.
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking.
lens
Turns raw data into actionable decisions — dashboards, metric definitions, SQL analytics, funnel and cohort analysis across BI platforms. Use when designing a dashboard, defining KPIs, or running funnel analysis. Trigger with "design a dashboard", "analyze our funnel".
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
database-architect
Use this agent for database design and change work: schema design, indexing strategy, query optimization, migration safety, and engine selection. Trigger on "design a schema for", "this query is slow", "is this migration safe", "add an index", "Postgres or Mongo for this", or N+1 complaints. Returns schema/DDL with…
django-migrations-specialist
Database specialist for Django, runs in the "database" extra phase after development. Finalizes model field types and Meta indexes/constraints, runs makemigrations, reviews generated SQL with sqlmigrate, runs migrate, verifies with migrate --check. Do NOT use for: application logic (django-architect), tests…