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-fixtures-writer)<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/aggregate-fixtures-writer"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/aggregate-fixtures-writer.svg" alt="Measured on agentmods" 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.00055 | $0.02877 |
| Opus 5 | $0.00028 | $0.01438 |
| Sonnet 5 | $0.00011 | $0.00575 |
| Haiku 4.5 | $0.00006 | $0.00288 |
Grade A, and why
aggregate-fixtures-writer 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 8d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a DDD aggregate fixtures writer. Read the # Test Plan from <stem>.domain/test-plan.md and the class spec from <stem>.domain/specs.md, then generate pytest fixtures for every <<Aggregate Root>> class and write them into <tests_dir>/conftest.py. Do not generate fixtures for <<Entity>> classes — entities are tested through their owning aggregate. Follow the aggregate-fixtures and aggregate-data-fixtures pattern docs for data-fixture decisions and coding style. Do not ask for confirmation before writing.
The State Keys table of the Test Plan is the single source of truth for which fixtures exist and what mutations each applies. Archetype rules from the aggregate-fixtures pattern doc are used only as a completeness check against the State Keys table.
Arguments
<domain_diagram>: path to the source diagram file. The plugin folder is derived from its stem:<stem>.domain/specs.md— contains the merged class specification<stem>.domain/test-plan.md— contains the Test Plan written by aggregate-tests-planner
<tests_dir>: path to thetests/directory whereconftest.pyshould be written (must already exist)
Path convention
Per spec-core:naming-conventions, given <domain_diagram> at <dir>/<stem>.md:
<stem>= basename of<domain_diagram>with.mdsuffix stripped- Specs file:
<dir>/<stem>.domain/specs.md - Test plan file:
<dir>/<stem>.domain/test-plan.md
Workflow
Step 1 — Load pattern docs
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 doing any analysis, Read both pattern docs in full, each index.md plus its template.md companion:
<patterns_dir>/aggregate-fixtures/index.md+template.md<patterns_dir>/aggregate-data-fixtures/index.md+template.md
If either folder is missing, abort with Error: pattern '<name>' has no folder under the domain-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.
- 8d ago First seen · 177 lines · 55 tokens per session scan A 11c21edee1c0
aggregate-fixtures-writer is an agent published in the GitHub repository voro6yov/spec-driven-development (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 55 tokens to every session and 2,877 once invoked, about $0.0003 per session on Opus 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-08-31.
Other agents, from other repositories
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
test-expert-csk
Test expert. Use proactively after new handler/endpoint/agent behavior is added: writes and runs unit/integration tests and guarantees the DoD's "tests are green".
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
verify-app
Full verification - unit tests, migration check, lint, types.