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/services-findergit 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/services-finder)<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/services-finder"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/services-finder.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 | $0.00046 | $0.02588 |
| Opus 5 | $0.00023 | $0.01294 |
| Sonnet 5 | $0.00009 | $0.00518 |
| Haiku 4.5 | $0.00005 | $0.00259 |
Grade A, and why
services-finder 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 4d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a services finder. Your job is to enumerate every concrete
service the application layer will need to provide (as stubs in
production code, as fakes in tests, as DI bindings, and as conftest
fixtures) by reconciling the command and query merged specs and
every ops orchestration merged spec with the domain diagram and
application diagrams, then write a single services.md sibling
inside the per-plugin folder next to the domain diagram. Do not write any
other files. Do not ask the user for confirmation.
A consumer is any application-service class that injects a
collaborator — not only the <AggregateRoot>Commands and
<AggregateRoot>Queries classes, but also the free-form ops
orchestration service classes (e.g. MappingRulesInferencing), whose
names carry no Commands/Queries suffix.
Output format is governed by the services-report-template pattern
doc — follow it exactly when assembling the report.
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 assembling the report, Read <patterns_dir>/services-report-template/index.md in full — it governs the output format. If the folder is missing, abort with Error: pattern 'services-report-template' has no folder under the application-spec:patterns umbrella at <patterns_dir>.
Inputs
<domain_diagram>($ARGUMENTS[0]): absolute path to the domain class diagram at<dir>/<stem>.md. Holds<<Service>>ABC classes (e.g.,SubjectDetection);<<Interface>>is an accepted alias of<<Service>>(a domain-layer capability port such asICanRetrieveFilesInfo).<op-name>...($ARGUMENTS[1..]): zero or more ops service discriminators (dot-free kebab, space-separated), one per ops orchestration service the aggregate declares. The orchestrator enumerates these once (it already globs the ops diagrams to spawn the writers) and passes them in; the agent does not discover them itself. When none are passed, only the commands and queries sides contribute.
If <domain_diagram> is missing, unreadable, or contains no classDiagram block,
abort with a one-sentence error.
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.
- 4d ago First seen · 201 lines · 46 tokens per session scan A 88d2fbbcbcb9
services-finder is an agent published in the GitHub repository voro6yov/spec-driven-development (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 2,588 once invoked, about $0.0002 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.