commands-methods-writer

commands-methods-writer is an agent for coding agents from voro6yov/spec-driven-development. It costs 37 tokens per session (5,570 once invoked), scanned A, original, Apache-2.0.

A coding agent that writes method specifications for a Commands application service from a domain class diagram and its command diagram. A method specification describes what an operation does and how it flows through the domain model.

In plain words
What is it for?
Use it to document the command operations of an aggregate's application service before implementation or review.
Why use it?
It removes the manual work of turning diagrams into consistently formatted service-method documentation. It also applies the project's required template and assumes command methods return the aggregate root.

Agent

Part of the application-spec plugin — 5 skills, 1 command, 26 agents shipped together

Install

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.

agentmods
npx agentmods add agents/voro6yov/spec-driven-development/commands-methods-writer
Clone the repo
git clone --depth 1 https://github.com/voro6yov/spec-driven-development

Or install application-spec, the plugin that ships this one along with the rest of its 5 skills, 1 command, 26 agents.

Wrote 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.

agentmods badge for commands-methods-writer

README.md
[![agentmods](https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/commands-methods-writer.svg)](https://agentmods.dev/agents/voro6yov/spec-driven-development/commands-methods-writer)
Your own site
<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/commands-methods-writer"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/commands-methods-writer.svg" alt="Measured on agentmods" height="20"></a>
Per session 37 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,570 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00037 $0.05570
Opus 5 $0.00018 $0.02785
Sonnet 5 $0.00007 $0.01114
Haiku 4.5 $0.00004 $0.00557

Measured 4d ago against content hash 72e62b8af295, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

commands-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 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.

plugins/application-spec/agents/commands-methods-writer.md · 269 lines

How it starts

The opening of the file, as written. The whole thing — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a command-application-service method specifier. Given a path to the domain class diagram, you derive the sibling commands diagram, parse both diagrams (the commands diagram describing an <AggregateRoot>Commands application service 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 flow shapes and 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>.

Application command methods in this codebase always return the aggregate root. Use that as a hard invariant — never infer a different return shape from the diagram, and never use the return type as a signal for factory vs. canonical detection.

Inputs

  • <domain_diagram> ($ARGUMENTS[0]): absolute path to the domain class diagram at <dir>/<stem>.md.

Path resolution

Per spec-core:naming-conventions ("Path resolution"). Recover <dir> and <stem> from <domain_diagram>, then derive:

  • <commands_diagram> = <dir>/<stem>.commands.md — the commands-side diagram this agent parses alongside the domain diagram. Per spec-core:naming-conventions Path-hygiene rule 6, build this strictly as <dir>/<stem>.commands.md from the supplied <domain_diagram>; it must live in the same directory as the domain diagram. Never locate it by globbing the tree, by matching the <AggregateRoot> class name, or by selecting a like-named file under a different aggregate's folder (e.g. for …/ruleset/ruleset.md the commands diagram is …/ruleset/ruleset.commands.md, never …/mapping-rule/mapping-rule.commands.md).
  • <plugin_dir> = <dir>/<stem>.application — the per-plugin folder for application-spec
  • <methods_output> = <plugin_dir>/commands.methods.md — the Method Specifications fragment.
  • <exceptions_output> = <plugin_dir>/commands.exceptions.md — the Application Exceptions stub (always written; _(none)_ if no exceptions are raised).

Read the full file on GitHub · 269 lines

Changes

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.

  1. 4d ago First seen · 269 lines · 37 tokens per session scan A 72e62b8af295

Subscribe to this mod's changes

commands-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 37 tokens to every session and 5,570 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.