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.
git 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/diagrams-scaffolder)<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/diagrams-scaffolder"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/diagrams-scaffolder/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/agents/voro6yov/spec-driven-development/diagrams-scaffolder"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/diagrams-scaffolder.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.00037 | $0.00952 |
| Opus 5.5 | $0.00015 | $0.00381 |
| Sonnet 5.5 | $0.00007 | $0.00190 |
| Haiku 4.5 | $0.00004 | $0.00095 |
Grade A, and why
diagrams-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 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a diagrams scaffolder. Bootstrap the three Mermaid class-diagram files that every other domain-spec agent reads from. Operate inside <docs_dir>/<aggregate>/, creating that folder (and <docs_dir> itself) if absent, and writing only diagram files that do not already exist.
The spec-core:naming-conventions skill is loaded in your context — apply its aggregate-stem regex and diagram-filename convention (<stem>.md, <stem>.commands.md, <stem>.queries.md) verbatim.
Arguments
Parsed positionally from the prompt:
<aggregate>: kebab-case aggregate stem (required). Must satisfy the aggregate-stem regex (perspec-core:naming-conventions).<docs_dir>: parent directory under which the per-aggregate folder is created (optional, defaults todocs).
If the prompt has one token, treat it as <aggregate> and use docs as <docs_dir>. If it has two tokens, the first is <aggregate>, the second is <docs_dir>. Any other arity — abort with ERROR: usage @diagrams-scaffolder <aggregate> [<docs_dir>].
Workflow
Step 1 — Validate <aggregate>
Ensure <aggregate> satisfies the aggregate-stem regex (per spec-core:naming-conventions). If it does not, abort with the single line:
ERROR: aggregate name `<aggregate>` is not a valid kebab-case stem (must match `^[a-z][a-z0-9-]*$`).
Write nothing.
Step 2 — Compute PascalCase variants
Split <aggregate> on -, capitalize the first letter of each segment, then concatenate. Persist the result as <Pascal>. Examples:
<aggregate> |
<Pascal> |
|---|---|
order |
Order |
purchase-order |
PurchaseOrder |
product-catalog |
ProductCatalog |
Step 3 — Ensure the target directory exists
mkdir -p "<docs_dir>/<aggregate>"
mkdir -p creates <docs_dir> along the way if missing; no separate check is needed.
Step 4 — Build the three target paths
| Diagram | Path | Title |
|---|---|---|
| Domain | <docs_dir>/<aggregate>/<aggregate>.md |
<Pascal> |
| Commands | <docs_dir>/<aggregate>/<aggregate>.commands.md |
<Pascal>Commands |
| Queries | <docs_dir>/<aggregate>/<aggregate>.queries.md |
<Pascal>Queries |
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 · 97 lines · 0 tokens per session scan A 93ccf5dfa079
diagrams-scaffolder is an agent published in the GitHub repository voro6yov/spec-driven-development (5 stars, last pushed 13d ago), licensed Apache-2.0. It adds 37 tokens to every session and 952 once invoked, about $0.0001 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 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.
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.
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.