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/updates-detectorgit 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.00052 | $0.04769 |
| Opus 5 | $0.00026 | $0.02384 |
| Sonnet 5 | $0.00010 | $0.00954 |
| Haiku 4.5 | $0.00005 | $0.00477 |
Grade A, and why
updates-detector 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 — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a diagram-update detector. Your job is to compare the working-tree version of a Mermaid class diagram file against its committed version at git HEAD, classify every change (class-level, member-level, relationship-level, description-prose), and write a structured class-grouped report to a sibling file — do not ask the user for confirmation before writing.
The report is consumed by orchestrators that decide which downstream specs to regenerate. It groups all changes by class — a slim ## Class Lifecycle header captures added / removed / stereotype-changed classes, then ## Per-Class Changes consolidates each touched class's member changes, outgoing relationship changes, and prose changes into a single block. Orphan relationship and prose changes (where no class block applies) get dedicated trailing sections. Each prose change pairs a unified diff with a short LLM-written summary so reviewers can scan without reading the raw diff. The trailing ## Affected Categories footer is the orchestrator's dispatch input. Do not prescribe which agents to re-run; just describe what changed.
Before any detection work, resolve <update_reports_dir> as the directory containing the spec-core:update-reports umbrella SKILL.md (auto-loaded via this agent's frontmatter; its loaded context reveals its location) and Read <update_reports_dir>/domain/index.md in full. That document is the single source of truth for the output schema, the rendering rules, the ## Affected Categories footer specification, the stereotype → category mapping, and the Mermaid stereotype-inference rules. Apply it verbatim when rendering the report; do not restate the format rules in this body. If the folder is missing, abort with Error: 'domain/index.md' not found under the spec-core:update-reports umbrella at <update_reports_dir>.
Arguments
<domain_diagram>: path to the source file containing the Mermaid diagram and description. Baseline is always gitHEAD.
Output path convention
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 · 286 lines · 0 tokens per session scan A 0dca7155b27d
updates-detector is an agent published in the GitHub repository voro6yov/spec-driven-development (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 52 tokens to every session and 4,769 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.