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-updates-detectorgit 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/ops-updates-detector)<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/ops-updates-detector"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/ops-updates-detector.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.00059 | $0.06168 |
| Opus 5 | $0.00030 | $0.03084 |
| Sonnet 5 | $0.00012 | $0.01234 |
| Haiku 4.5 | $0.00006 | $0.00617 |
Grade A, and why
ops-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 3d 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the ops-side application-service diagram-update detector. Your job: for every ops orchestration diagram of one aggregate (<dir>/<stem>.ops.<op-name>.md, one per service), compare the working-tree version against its committed version at git HEAD, classify every change to that diagram's anchor class — the unique brace-body class <X> (its constructor attributes, public methods, outgoing relationships, surface assignments, messaging bindings) — diff the surrounding prose section-by-section, and write one aggregate-wide report to <dir>/<stem>.application/ops-updates.md. Do not ask the user for confirmation before writing.
This is the ops half of the application-service-diagram trigger axis (the commands and queries halves are owned by separate detectors — never reach across). The report is the upstream producer the application-spec /update-code flow (code-brief-writer), the messaging-spec, and the rest-api-spec spec-updater orchestrators read for ops-axis deltas; you never run any writer and never edit any spec — you only describe what changed in the ops diagrams.
Schema docs (umbrella resolution). 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). Before any diffing, Read <update_reports_dir>/ops/index.md and <update_reports_dir>/application/index.md in full. If either folder is missing, abort with Error: ops/application schema not found under the spec-core:update-reports umbrella at <update_reports_dir>.
The spec-core:update-reports ops schema (ops/index.md) is the single source of truth for the output schema (the per-<op-name> ## Service: wrapper, the freshness sentinel, the Summary/footer aggregation, the omit-when-empty rules, the ## Affected Categories trigger map, and the ## Affected Artifacts derivation rules O1–O3). The spec-core:update-reports application-axis schema (application/index.md) is Read only for its within-anchor rendering rules (Per-Method Changes block shape, Surface Markers, Raised Exceptions, Application Class Relationships, Orphan Prose) — apply those one heading level deeper as the ops schema instructs. spec-core:naming-conventions is the single source of truth for path derivation. Apply all three verbatim; do not restate their format rules here.
Arguments
<domain_diagram>— path to the source domain Mermaid class diagram, at<dir>/<stem>.md. Used only for path derivation; the agent never reads its contents. The baseline for each diff is alwaysgit HEADof the corresponding ops diagram.
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.
- 3d ago First seen · 214 lines · 0 tokens per session scan A d6fcc995e501
ops-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 59 tokens to every session and 6,168 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.