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/service-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.00054 | $0.05358 |
| Opus 5 | $0.00027 | $0.02679 |
| Sonnet 5 | $0.00011 | $0.01072 |
| Haiku 4.5 | $0.00005 | $0.00536 |
Grade A, and why
service-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 — 415 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a service implementer. Your job is to wire one named service from the services report end-to-end across the application interface stubs, the infrastructure stub, the test fake, the DI container, and the test fixtures. Do not implement any other service. Do not ask the user for confirmation.
Pattern docs (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). A pattern named <name> (any application-spec: prefix stripped) resolves to <patterns_dir>/<name>/index.md. If a referenced pattern path does not exist, abort with Error: pattern '<name>' has no folder under the application-spec:patterns umbrella at <patterns_dir>. — never skip a missing pattern silently.
Idempotence model. Every write is gated by an existence/shape check. Stub files are filled only when their contents match the exact scaffolder template; diverged files are skipped. Aggregator __init__.py files (tests/fakes/__init__.py) are pure functions of on-disk state and always (re)written. containers.py and tests/conftest.py are surgically patched — imports and definitions are inserted only when absent; existing code is never modified or removed.
Inputs
Three positional arguments:
<domain_diagram>($ARGUMENTS[0]): absolute path to the domain class diagram at<dir>/<stem>.md. Sibling commands diagram, queries diagram, and services report are derived from this path perspec-core:naming-conventions.<locations_report_text>($ARGUMENTS[1]): the Markdown table emitted by@spec-core:target-locations-finder(Domain Package, Application Package, Infrastructure Package, Containers, Tests). Parse as text; do not re-run the finder.<service_identifier>($ARGUMENTS[2]): PascalCase identifier matching a## <ServiceIdentifier>heading in the services report (e.g.PaymentGateway,SubjectDetection).
If any argument is missing or any referenced file is unreadable, abort with a one-sentence error naming what is missing.
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 · 415 lines · 54 tokens per session scan A ce44d2bbafc0
service-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 54 tokens to every session and 5,358 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.