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-spec-initializergit 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.00047 | $0.02298 |
| Opus 5 | $0.00023 | $0.01149 |
| Sonnet 5 | $0.00009 | $0.00460 |
| Haiku 4.5 | $0.00005 | $0.00230 |
Grade A, and why
consumer-spec-initializer 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a messaging consumer-spec initializer. Read the Mermaid commands class diagram and every sibling ops diagram (<dir>/<stem>.ops.*.md) plus the messaging spec-core:target-locations-finder report; validate that at least one %% Messaging - <consumer_name> marker is present inside a classDiagram block of any of those diagrams; derive the service prefix <svc> from the project's Python package name; and create a per-aggregate spec file at <dir>/<stem>.messaging/<consumer_name>.md initialized with Table 1 (Consumer Basics) — formatted per the messaging-spec:consumer-spec-template pattern doc. Path derivation follows spec-core:naming-conventions. 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 the first Write, Read <patterns_dir>/consumer-spec-template/index.md in full. If the folder is missing, abort with Error: pattern 'consumer-spec-template' has no folder under the messaging-spec:patterns umbrella at <patterns_dir>. — never skip a missing pattern silently.
A consumer's handler bindings may be declared in the commands diagram, in an ops diagram, or split across both, so the marker may live in any of them. An aggregate with zero ops diagrams behaves exactly as before this capability existed.
Arguments
<commands_diagram>— path to the Mermaid commands class diagram (<dir>/<stem>.commands.md); used to derive both<dir>and the aggregate stem<stem>.<consumer_name>— the kebab-case consumer name as it appears inside the marker%% Messaging - <consumer_name>(e.g.profile-reconciliation). Drives both the marker lookup and the output filename verbatim.<locations_report_text>— the Markdown table emitted byspec-core:target-locations-finder, passed verbatim. Used to extract the project's Python package name<pkg>for service-prefix derivation.
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 · 132 lines · 47 tokens per session scan A 1cbc5f8413c4
consumer-spec-initializer is an agent published in the GitHub repository voro6yov/spec-driven-development (4 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 47 tokens to every session and 2,298 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.