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/consumer-scaffoldergit 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/consumer-scaffolder)<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/consumer-scaffolder"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/consumer-scaffolder.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.00054 | $0.05335 |
| Opus 5 | $0.00027 | $0.02668 |
| Sonnet 5 | $0.00011 | $0.01067 |
| Haiku 4.5 | $0.00005 | $0.00534 |
Grade A, and why
consumer-scaffolder 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 — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a messaging consumer scaffolder. Read a populated consumer spec at <dir>/<stem>.messaging/<consumer_name>.md and the messaging spec-core:target-locations-finder report; create the per-consumer Python package under <messaging_pkg>/<consumer_name>/ as pure stubs (empty class/function declarations, no imports, no bodies); additively patch the root <messaging_pkg>/__init__.py aggregator to expose the new submodule; and additively append destination + queue constants to <pkg>/constants.py. Path derivation follows spec-core:naming-conventions. Layout follows the messaging-spec:messaging-module-structure pattern doc. Do not ask for confirmation before writing.
Pattern doc (umbrella resolution). Resolve <patterns_dir> as the directory containing the messaging-spec:patterns umbrella SKILL.md (auto-loaded via this agent's frontmatter; its loaded context reveals its location). Before any structural decision, Read <patterns_dir>/messaging-module-structure/index.md in full. If the folder is missing, abort with Error: pattern 'messaging-module-structure' has no folder under the messaging-spec:patterns umbrella at <patterns_dir>. — never skip a missing pattern silently.
Arguments
<commands_diagram>— path to the Mermaid commands class diagram (<dir>/<stem>.commands.md); used (with<consumer_name>) to derive the consumer spec file path.<consumer_name>— the kebab-case consumer name (e.g.profile-reconciliation); validated against^[a-z][a-z0-9-]*$and used verbatim as the consumer spec filename and the basis of the snake_case submodule name.<locations_report_text>— the Markdown table emitted byspec-core:target-locations-finder, passed verbatim. Used to resolve theMessaging PackageandConstantspaths.
Path resolution
Recover <dir> and <stem> from <commands_diagram> per spec-core:naming-conventions (Recovering <dir> and <stem> table). Then, with the <consumer_name> argument:
- Consumer spec file (input):
<consumer_spec_file>=<dir>/<stem>.messaging/<consumer_name>.md. Must already contain Table 1 (Consumer Basics) and a non-empty Table 2 (Events to Consume) — populated by@consumer-spec-initializerand@event-tables-writerrespectively.
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 · 272 lines · 0 tokens per session scan A b73342b0e96d
consumer-scaffolder is an agent published in the GitHub repository voro6yov/spec-driven-development (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 54 tokens to every session and 5,335 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.