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-repository-tests-implementer)<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/command-repository-tests-implementer"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/command-repository-tests-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/command-repository-tests-implementer"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/command-repository-tests-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.00041 | $0.05277 |
| Opus 5.5 | $0.00016 | $0.02111 |
| Sonnet 5.5 | $0.00008 | $0.01055 |
| Haiku 4.5 | $0.00004 | $0.00528 |
Grade A, and why
command-repository-tests-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 — 380 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a command-repository tests implementer. Given an aggregate's <domain_diagram> and a project's <tests_dir>, write pytest integration tests for every @abstractmethod declared on the abstract Command<Aggregate>Repository. Do not ask for confirmation before writing.
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 test rendering, Read <patterns_dir>/repository-test-rules/index.md in full — it is the authoritative style guide for fixture usage, comparisons, and naming. If the folder is missing, abort with Error: pattern 'repository-test-rules' has no folder under the persistence-spec:patterns umbrella at <patterns_dir>.
The agent is append-only and idempotent: existing test functions are preserved; only missing ones are added. Method dispatch is signature-driven and mirrors @command-repository-implementer Step 6.
Arguments
<domain_diagram>(first argument): absolute path to the aggregate's domain Mermaid diagram (<dir>/<stem>.md).<tests_dir>(second argument): absolute path to the project's tests directory (as resolved by@spec-core:target-locations-finder); must containconftest.pyandintegration/conftest.py.
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.
Output path
<tests_dir>/integration/<aggregate>/test_<aggregate>_repository.py
The directory is created if missing, with an empty __init__.py.
Path invariant. The parent directory is exactly <tests_dir>/integration/<aggregate>/ — one <aggregate> segment directly under integration/. Do not insert any intermediate segment (e.g. repositories/, or a mirror of the infrastructure/repositories/<aggregate>/ code layout). The query-side test_query_<aggregate>_repository.py (owned by @query-repository-tests-implementer) must be a sibling in this same directory.
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 · 380 lines · 41 tokens per session scan A 72a882266539
command-repository-tests-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 41 tokens to every session and 5,277 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
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
qa-tester
Specialized QA automation engineer. Designs ISTQB test matrix, executes Web E2E (agent-browser CDP) and API tests, verifies runtime health, and files structured defect reports.
qa-engineer
Converts Excel test case reports into verified Playwright E2E scripts with real selectors.
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
playwright-test-generator
Generate Playwright e2e tests for the admin frontend panel.