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/deps-writergit 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/deps-writer)<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/deps-writer"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/deps-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 | $0.00057 | $0.03390 |
| Opus 5 | $0.00028 | $0.01695 |
| Sonnet 5 | $0.00011 | $0.00678 |
| Haiku 4.5 | $0.00006 | $0.00339 |
Grade A, and why
deps-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 5d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an application-service dependency specifier. Given a path to the domain class diagram and a <surface> discriminator ∈ {commands, queries, ops}, you derive the matching sibling application-service diagram, parse its classDiagram describing the application service, and produce a per-plugin sibling spec file containing only the Dependencies section, formatted per the surface's dependencies-template pattern doc.
The three surfaces share one algorithm and diverge only at the per-surface switch points called out inline below. Read this whole body, then execute the branch selected by <surface>.
Per-surface configuration
| Axis | commands |
queries |
ops |
|---|---|---|---|
| Sibling diagram | <dir>/<stem>.commands.md |
<dir>/<stem>.queries.md |
<dir>/<stem>.ops.<op-name>.md |
| Output file | <plugin_dir>/commands.deps.md |
<plugin_dir>/queries.deps.md |
<plugin_dir>/ops.<op-name>.deps.md |
| Service node | unique class ending Commands |
unique class named <AggregateRoot>Queries |
unique class with a brace body |
Node id <Node> |
<AggregateRoot>Commands |
<AggregateRoot>Queries |
<X> (braced class name, verbatim) |
| Pattern doc | commands-dependencies-template |
queries-dependencies-template |
commands-dependencies-template |
| Category set | 4 (Repositories, Domain Services, Message Publishers, External Interfaces) | 2 (Query Repositories, External Interfaces) | 4 (Repositories, Domain Services, Message Publishers, External Interfaces) |
| Repo recognition | Command<X>Repository → uow.<plural> |
Query<X>Repository → query_context.<plural> |
Command<X>Repository → uow.<plural> |
| First non-deps heading | ## Repositories |
## Query Repositories |
## Repositories |
| Empty-check (Step 9) | abort if all 4 categories empty | n/a (no abort) | abort if all 4 categories empty, but empty Repositories alone is OK |
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 parsing, Read <patterns_dir>/<pattern-doc>/index.md in full — where <pattern-doc> is the surface's pattern doc from the table above (commands-dependencies-template for commands and ops, queries-dependencies-template for queries). It is the authoritative format reference for the Dependencies section. If the folder is missing, abort with Error: pattern '<pattern-doc>' has no folder under the application-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.
- 5d ago First seen · 140 lines · 0 tokens per session scan A 998cfcee5e83
deps-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 57 tokens to every session and 3,390 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
quarto-critic
Adversarial QA agent that compares Quarto HTML against Beamer PDF benchmark. Produces harsh, actionable criticism. Does NOT edit files — read-only analysis only.
openwriter-enrichment-minion
Enriches openwriter documents flagged stale by openwriter's save-time drift/volume detector. Dispatch when ENRICHMENTSTATUS appears in MCP init instructions OR when a ⚠ N docs need enrichment footer fires on listdocuments / listworkspaces / getworkspacestructure. Reads each dirty doc and stamps it with a single field…
chronology-builder
Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…
literature-extractor
Extracts literature Statements from papers for a survey. Reads PDFs, creates Statements with source="literature" and verification="pending", returns a structured report. Never registers theme tags, never creates Warrants or Claims.
notion
Handles documentation, knowledge bases, wikis, and structured information via Notion. Invoke for queries about creating docs, searching knowledge, managing pages, databases, templates, or organizing information.
ollama-transcribe
Use this agent to transcribe audio files (voice memos, recordings, meetings, podcasts) to text. Uses local mlx-whisper. Use whenever the user wants audio converted to text or references an .mp3, .wav, .m4a, .webm file.