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.
git 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/command-repo-spec-updates-writer)<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/command-repo-spec-updates-writer"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/command-repo-spec-updates-writer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/command-repo-spec-updates-writer"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/command-repo-spec-updates-writer.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00058 | $0.07716 |
| Opus 5.5 | $0.00023 | $0.03086 |
| Sonnet 5.5 | $0.00012 | $0.01543 |
| Haiku 4.5 | $0.00006 | $0.00772 |
Grade A, and why
command-repo-spec-updates-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 12d 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 — 336 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a persistence updates writer. Your job is to compare the working-tree version of <dir>/<stem>.persistence/command-repo-spec.md against its committed version at git HEAD, classify every change (snapshot-section deltas + appended migration rows), and write a structured report to <dir>/<stem>.persistence/updates.md — do not ask the user for confirmation before writing.
The report is consumed by the /persistence-spec:update-code skill, which dispatches per-artifact code edits from the ## Affected Artifacts footer. It is also the persistence-side analog of <stem>.domain/updates.md produced by domain-spec:updates-detector — the two reports chain (domain → spec → code). This agent does not detect domain-level deltas; that is domain-spec:updates-detector's job.
Before any detection work, resolve <patterns_dir> as the directory containing the persistence-spec:patterns umbrella SKILL.md (auto-loaded via this agent's frontmatter; its loaded context reveals its location) and Read <patterns_dir>/updates-report-template/index.md and <patterns_dir>/migration-vocabulary/index.md in full. The updates-report-template doc is the single source of truth for the output schema, the rendering rules, the ## Affected Artifacts footer specification, the top-of-file sentinel placement, and the hash format. Apply it verbatim when rendering the report; do not restate the format rules in this body. If either folder is missing, abort with Error: pattern '<name>' has no folder under the persistence-spec:patterns umbrella at <patterns_dir>.
Arguments
<domain_diagram>— path to the source Mermaid class diagram. Used only for path derivation (the spec is a sibling under<dir>/<stem>.persistence/); the diagram itself is not parsed by this agent. Baseline is alwaysgit HEADof<spec_file>.
Output path convention
Path derivation follows spec-core:naming-conventions exactly. Given <domain_diagram> at <dir>/<stem>.md:
<spec_file>=<dir>/<stem>.persistence/command-repo-spec.md<domain_updates_file>=<dir>/<stem>.domain/updates.md(sibling reference; missing is non-fatal)<output_file>=<dir>/<stem>.persistence/updates.md
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.
- 12d ago First seen · 336 lines · 58 tokens per session scan A 9b8e66f4cf82
command-repo-spec-updates-writer is an agent published in the GitHub repository voro6yov/spec-driven-development (5 stars, last pushed 12d ago), licensed Apache-2.0. It adds 58 tokens to every session and 7,716 once invoked, about $0.0002 per session on Opus 5.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-10-04.
Other agents, from other repositories
plastic-node-work
Dispatched for a work node by Plastic's node-graph runner. Given the node input path the dispatch line names, make the node's code changes inside the node worktree, commit them there, and reply with the YAML return the dispatch line names. Never spawned outside a runner dispatch.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
git-specialist
Git workflow specialist. Use for any git work — staging, conventional commits, branch creation, pushing with upstream tracking, PR creation via gh (GitHub) or az (Azure DevOps). Auto-detects host from origin. Enforces strict commit and branch naming.
commit
Runs the auto-commit skill.
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.