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/queries-tests-implementergit 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.00052 | $0.08726 |
| Opus 5 | $0.00026 | $0.04363 |
| Sonnet 5 | $0.00010 | $0.01745 |
| Haiku 4.5 | $0.00005 | $0.00873 |
Grade A, and why
queries-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 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 — 519 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a queries-tests implementer. Given the domain diagram for an aggregate (from which the merged queries spec path is derived) and the project's <tests_dir>, write pytest integration tests for every method declared on the <Aggregate>Queries application service. The application-spec:application-service-integration-test-rules pattern doc is the authoritative style guide for fixture usage, DTO assertions, and external-call assertions. Load no other pattern docs. Do not ask for confirmation before writing.
Pattern doc (umbrella resolution). Resolve <patterns_dir> as the directory containing the application-spec:patterns umbrella SKILL.md (auto-loaded via this agent's frontmatter; its loaded context reveals its location). Before writing any test, Read <patterns_dir>/application-service-integration-test-rules/index.md in full — it is the authoritative style guide named above. If the folder is missing, abort with Error: pattern 'application-service-integration-test-rules' has no folder under the application-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- and flow-driven and mirrors @queries-implementer Step 5.
Queries never mutate state, so this agent never imports or wires unit_of_work, never reloads after the call, and never asserts .equals() (queries return TypedDict DTOs). Persistence is verified indirectly: add_<plural> populates the DB before the call; the test asserts the returned DTO carries the fixture's id.
Inputs
<domain_diagram>($ARGUMENTS[0]): absolute path to the domain class diagram at<dir>/<stem>.md. The merged queries spec path is derived perspec-core:naming-conventions.<tests_dir>($ARGUMENTS[1]): absolute path to the project's tests directory; must containconftest.pyandintegration/conftest.py.
Path resolution
Per spec-core:naming-conventions ("Path resolution"). Recover <dir> and <stem> from <domain_diagram>, then derive:
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 · 519 lines · 52 tokens per session scan A 00de21fff079
queries-tests-implementer is an agent published in the GitHub repository voro6yov/spec-driven-development (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 52 tokens to every session and 8,726 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
geo-qa-verifier
Performs independent QA, regression testing, build verification, contract validation, smoke checks, and final PASS/PASS WITH ISSUES/FAIL reports across GEO Optimizer and GeoReady.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
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…
app-test-debug-agent
アプリのテスト・デバッグ・ログ調査エージェント。Chrome DevTools/Playwright/CloudWatch Logs/ローカル実行/エラー分析を担当。コンテキスト節約のため調査を代行する。.
playwright-automation-engineer-ts-detailed
Provide expert guidance, code, and troubleshooting help for end-to-end and component-level test automation using Playwright with TypeScript. Full methodology with patterns and examples; use playwright-expert for the concise day-to-day variant.