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 skills add voro6yov/spec-driven-development --skill derive-query-partgit 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/skills/voro6yov/spec-driven-development/derive-query-part)<a href="https://agentmods.dev/skills/voro6yov/spec-driven-development/derive-query-part"><img src="https://agentmods.dev/badge/skills/voro6yov/spec-driven-development/derive-query-part/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/skills/voro6yov/spec-driven-development/derive-query-part"><img src="https://agentmods.dev/badge/skills/voro6yov/spec-driven-development/derive-query-part.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.00074 | $0.01246 |
| Opus 5.5 | $0.00030 | $0.00498 |
| Sonnet 5.5 | $0.00015 | $0.00249 |
| Haiku 4.5 | $0.00007 | $0.00125 |
Grade A, and why
derive-query-part 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a query-part-derivation orchestrator. A domain diagram has a command
part (aggregate root, Command<X>Repository, children, events, TypedDicts) and
a query part (the read-side classes). Your job: derive the query part from the
command part, settle the few non-mechanical decisions by interviewing the user,
and write the result into the diagram in place.
You do not write the query classes yourself — you interview, then delegate the
write to the model-diagrams:query-part-deriver agent.
Inputs
$ARGUMENTS is the verbatim user input: a single token <diagram_file> — an
absolute or repo-relative path to a Mermaid domain diagram.
Reject and stop with a one-line error if:
<diagram_file>does not exist.- It does not end in
.md, or it ends in.commands.md/.queries.md— this skill operates only on a domain diagram (<stem>.md).
Workflow
Step 1 — Load the derivation rules
Invoke the model-diagrams:query-derivation skill via the Skill tool. Its rules
are binding — every decision below is grounded in it.
Step 2 — Read and parse the command part
Read <diagram_file> in full. From the classDiagram block identify:
- The
<<Aggregate Root>>class<X>— its fields and computed properties. - The
Command<X>Repositoryand its lookup methods. - Child
<<Entity>>/<<Value Object>>classes reachable from<X>. - Command-side
<<TypedDict>>classes (reuse candidates). - Whether a query part already exists (any of
Query<X>Repository,<X>Info,<X>Filtering,Brief<X>Info,<X>ListResult).
If no <<Aggregate Root>> is present, stop with a one-line error — there is no
command part to project.
Step 3 — Compute the draft and the decision candidates
Apply the query-derivation rules to derive the draft query part. While doing so,
collect the three feedback points:
- Alternate lookups — every
Command<X>Repositorymethod returning<X>that is not<x>_of_id. Each is a candidatefind_<x>_by_*. <X>Infofields — the full mirrored field list (after flattening). Any of them is an omission candidate.<X>Filteringfields — the proposed default filterable-scalar set.
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 · 108 lines · 74 tokens per session scan A c79a4ca3c7d0
derive-query-part is a skill published in the GitHub repository voro6yov/spec-driven-development (5 stars, last pushed 13d ago), licensed Apache-2.0. It adds 74 tokens to every session and 1,246 once invoked, about $0.0003 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 skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…