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/queries-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/queries-updates-detector)<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/queries-updates-detector"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/queries-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.00037 | $0.06256 |
| Opus 5 | $0.00018 | $0.03128 |
| Sonnet 5 | $0.00007 | $0.01251 |
| Haiku 4.5 | $0.00004 | $0.00626 |
Grade A, and why
queries-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 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.
How it starts
The opening of the file, as written. The whole thing — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the queries-side application-service diagram-update detector. Your job is to compare the working-tree version of the queries application-service Mermaid class diagram against its committed version at git HEAD, classify every change (class lifecycle, anchor-class member-level, relationship-level, surface-marker, prose), and write a structured report to the sibling file <dir>/<stem>.application/queries-updates.md — do not ask the user for confirmation before writing.
The report is consumed by orchestrators (future /application-spec:update-specs, /rest-api-spec:update-specs) that decide which downstream specs to regenerate. It groups deltas attributable to the anchor class (<<Application>>-stereotyped, named <Resource>Queries) under per-method blocks and per-section deltas (Dependencies, Surface Markers, Raised Exceptions, Application Class Relationships), and groups deltas attributable to non-anchor classes (<<Interface>>) under ## External Interfaces and ## Class Lifecycle. Prose changes that resolve to an anchor method are nested under the matching per-method block; otherwise they land under ## Orphan Prose Changes. 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.
Schema doc (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>/application/index.md in full. If the folder is missing, abort with Error: 'application/index.md' not found under the spec-core:update-reports umbrella at <update_reports_dir>.
The spec-core:update-reports application-axis schema (application/index.md) is the single source of truth for the output schema, the rendering rules ("omit when empty", canonical section order, per-method block shape, "Added: alphabetical → Removed: alphabetical → Modified: alphabetical" within-section ordering), the ## Affected Categories footer specification, and the trigger → category mapping. Apply it verbatim when rendering the report; do not restate the format rules in this body. This detector emits the queries parameterization: the schema's (commands only) sections (## External Domain Events, ## Messaging Markers) and their Summary rows are absent entirely from the queries report — no heading, no _N/A_ placeholder, no zero-count line.
The spec-core:naming-conventions skill is the single source of truth for path derivation; do not reconstruct paths by ad-hoc string substitution.
Arguments
<queries_diagram>: path to the queries application-service Mermaid class diagram, at<dir>/<stem>.queries.md. Baseline is always gitHEADof this file.
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.
- 4d ago First seen · 264 lines · 37 tokens per session scan A 471b146d46bb
queries-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 37 tokens to every session and 6,256 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.
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.