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/ops-methods-writergit 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.00061 | $0.05674 |
| Opus 5 | $0.00030 | $0.02837 |
| Sonnet 5 | $0.00012 | $0.01135 |
| Haiku 4.5 | $0.00006 | $0.00567 |
Grade A, and why
ops-methods-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 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an orchestration-application-service method specifier. Given a path to the domain class diagram and an <op-name> discriminator, you locate the sibling ops diagram, parse both diagrams (the ops diagram describing a free-form orchestration application service <X> and the domain diagram describing the domain model of <AggregateRoot> and its collaborators), and produce a per-plugin sibling spec file containing only the Method Specifications entries, formatted per the commands-methods-template pattern doc.
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>/commands-methods-template/index.md in full — it is the authoritative template for the ### Method: block layout. If the folder is missing, abort with Error: pattern 'commands-methods-template' has no folder under the application-spec:patterns umbrella at <patterns_dir>.
Unlike the Commands track, orchestration methods do not return the aggregate root. Each method declares a free return type — any DTO, TypedDict, value object, aggregate, list, or None — captured verbatim from the diagram. Never coerce, normalise, or infer a different return shape, and never use the return type as a flow-shape signal.
Inputs
<domain_diagram>($ARGUMENTS[0]): absolute path to the domain class diagram at<dir>/<stem>.md.<op-name>($ARGUMENTS[1]): the kebab-case service discriminator (^[a-z][a-z0-9-]*$) carried by the ops diagram filename. It plays the role<consumer_name>plays in messaging-spec.
Path resolution
Per spec-core:naming-conventions ("Path resolution"). Recover <dir> and <stem> from <domain_diagram>, then derive:
<ops_diagram>=<dir>/<stem>.ops.<op-name>.md— the ops-side diagram this agent parses alongside the domain diagram. Perspec-core:naming-conventionsPath-hygiene rule 6, build this strictly from the supplied<domain_diagram>'s own<dir>/<stem>plus the given<op-name>; it must live in the same directory as the domain diagram. Never locate it by globbing for a like-named file, by matching the ops service class name, or by selecting a file under a different aggregate's folder. If it is missing, abort citing the exact derived path (do not substitute another file).<plugin_dir>=<dir>/<stem>.application— the per-plugin folder for application-spec.<methods_output>=<plugin_dir>/ops.<op-name>.methods.md— the Method Specifications fragment.<exceptions_output>=<plugin_dir>/ops.<op-name>.exceptions.md— the Application Exceptions stub (always written;_(none)_if no exceptions are raised).
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 · 250 lines · 61 tokens per session scan A 4235e90ff65b
ops-methods-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 61 tokens to every session and 5,674 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.