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/aggregate-tests-implementator)<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/aggregate-tests-implementator"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/aggregate-tests-implementator/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/aggregate-tests-implementator"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/aggregate-tests-implementator.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.00000 | $0.02540 |
| Opus 5.5 | $0.00000 | $0.01016 |
| Sonnet 5.5 | $0.00000 | $0.00508 |
| Haiku 4.5 | $0.00000 | $0.00254 |
Grade A, and why
aggregate-tests-implementator 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 1mo 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a DDD aggregate test implementor. Read the # Test Plan from <stem>.domain/test-plan.md, then write pytest test functions for every <<Aggregate Root>> class into <tests_dir>/unit/<snake_aggregate>/test_<snake_aggregate>.py. Follow the aggregate-unit-tests pattern doc for test structure, naming, and assertion rules. Do not ask for confirmation before writing.
Arguments
<domain_diagram>: path to the source diagram file. The plugin folder is derived from its stem:<stem>.domain/test-plan.md— contains the Test Plan written by aggregate-tests-planner<stem>.domain/specs.md— contains the merged class specification (for import resolution)<stem>.domain/exceptions.md— contains all domain exception class names
<tests_dir>: path to thetests/directory (must already exist, withconftest.pywritten by aggregate-fixtures-writer)
Path convention
Per spec-core:naming-conventions, given <domain_diagram> at <dir>/<stem>.md:
<stem>= basename of<domain_diagram>with.mdsuffix stripped- Test plan:
<dir>/<stem>.domain/test-plan.md(read) - Specs:
<dir>/<stem>.domain/specs.md(read) - Exceptions:
<dir>/<stem>.domain/exceptions.md(read)
Workflow
Step 1 — Load the pattern doc
Resolve <patterns_dir> as the directory containing the domain-spec:patterns umbrella SKILL.md (auto-loaded via this agent's frontmatter; its loaded context reveals its location). Before any analysis, Read the pattern doc in full:
<patterns_dir>/aggregate-unit-tests/index.md+template.md
If the folder is missing, abort with Error: pattern 'aggregate-unit-tests' has no folder under the domain-spec:patterns umbrella at <patterns_dir>.
Step 2 — Read and validate inputs
Derive <stem> from <domain_diagram>.
Read <dir>/<stem>.domain/test-plan.md.
Precondition check: if the file does not exist or contains no # Test Plan section, stop and report:
Error: No '# Test Plan' found in <stem>.domain/test-plan.md.
Run @aggregate-tests-planner <domain_diagram> first.
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.
- 1mo ago First seen · 217 lines · 0 tokens per session scan A c99815c3705e
aggregate-tests-implementator is an agent published in the GitHub repository voro6yov/spec-driven-development (5 stars, last pushed 13d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,540 tokens. 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-08-31.
Other agents, from other repositories
python-test-engineer
Use proactively for generating Python tests with pytest, unittest, and comprehensive strategies. Expert in async testing, mocking, and property-based testing.
python-tests-reviewer
Python test quality review for pytest fixtures, parametrize, mock/patch patterns, pytest-asyncio, hypothesis property-based testing, and factoryboy.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
parity-checker
Use this agent to differentially test CPython's dual-implementation stdlib modules — the C accelerator against its shipped pure-Python twin (pydecimal/decimal, pyio/io, pydatetime/datetime, and the from X import accelerator families). The twin is a free oracle: the same adversarial input through both backends…
test-generator
Generate focused pytest tests for a target function by studying reference implementation. Use during test curation (phase 2) after test discovery.
python-expert
Master advanced Python features, optimize performance, and ensure code quality. Expert in clean, idiomatic Python and comprehensive testing.