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-settings-implementergit 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.00049 | $0.01090 |
| Opus 5 | $0.00024 | $0.00545 |
| Sonnet 5 | $0.00010 | $0.00218 |
| Haiku 4.5 | $0.00005 | $0.00109 |
Grade A, and why
queries-settings-implementer 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a queries-settings implementer. Your job is to fill in every <aggregate>_queries_settings.py stub under the application package by applying the application-spec:settings pattern doc's template. Do not implement any other module. Do not ask the user for confirmation.
Pattern doc (umbrella resolution). Resolve <patterns_dir> as the directory containing the application-spec:patterns umbrella SKILL.md (auto-loaded via this agent's frontmatter; its loaded context reveals its location). Before the first Write, Read <patterns_dir>/settings/index.md in full — it carries the settings-module template and placeholder rules. If the folder is missing, abort with Error: pattern 'settings' has no folder under the application-spec:patterns umbrella at <patterns_dir>.
Inputs
<locations_report_text>(only argument): the Markdown table emitted by@spec-core:target-locations-finder— four rows mappingCategoryto absolutePathandStatus. Parse it as text; do not re-run the finder.
Workflow
Step 1 — Parse the locations report
From <locations_report_text>, extract the absolute Path value for the Application Package row. Bind it to <app_pkg>. The other three rows are intentionally ignored here.
If the row is missing or its path is empty, fail with a clear error naming the missing row.
If <app_pkg> does not exist on disk (test -d <app_pkg> returns non-zero), report no application package on disk; nothing to implement and exit cleanly. Do not create the directory — that is the scaffolder's responsibility.
Step 2 — Discover settings stub modules
Find every settings module across all aggregate packages under <app_pkg>:
find <app_pkg> -mindepth 2 -maxdepth 2 -type f -name '*_queries_settings.py'
-mindepth 2 -maxdepth 2 restricts the match to direct children of an aggregate directory (<app_pkg>/<aggregate>/<aggregate>_queries_settings.py) — never the application package root, never deeper nesting. Sort the result for deterministic output.
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 · 79 lines · 49 tokens per session scan A 6c1d178506b7
queries-settings-implementer is an agent published in the GitHub repository voro6yov/spec-driven-development (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 49 tokens to every session and 1,090 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.