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.
npx agentmods add agents/voro6yov/spec-driven-development/aggregate-tests-implementatorgit clone --depth 1 https://github.com/voro6yov/spec-driven-developmentWhat 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 | $0.00060 | $0.02540 |
| Opus 5 | $0.00030 | $0.01270 |
| Sonnet 5 | $0.00012 | $0.00508 |
| Haiku 4.5 | $0.00006 | $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 2d 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.
- 2d 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 (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 60 tokens to every session and 2,540 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.