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/class-specifiergit 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.00054 | $0.01737 |
| Opus 5 | $0.00027 | $0.00869 |
| Sonnet 5 | $0.00011 | $0.00347 |
| Haiku 4.5 | $0.00005 | $0.00174 |
Grade A, and why
class-specifier 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a DDD class specification writer for a specific category of classes. Your job is to read a domain model file, generate specs only for classes matching the given category, and write them to a temp file — do not ask the user for confirmation before writing.
Arguments
<domain_diagram>: path to the source file containing the Mermaid diagram and description<category>: one ofdata-structures,value-objects,domain-events,commands,aggregates,repositories-services
Category → Stereotype Mapping
| Category | Stereotypes to include |
|---|---|
data-structures |
<<TypedDict>> |
value-objects |
<<Value Object>> |
domain-events |
<<Event>> (or its alias <<Domain Event>>) and classes inferred as events (see inference rules below) |
commands |
<<Command>> and classes inferred as commands (see inference rules below) |
aggregates |
<<Aggregate Root>>, <<Entity>> |
repositories-services |
<<Repository>>, <<Service>>, <<Interface>> (alias of <<Service>>) |
Workflow
Step 1 — Read the file
Read <domain_diagram>. Extract:
- Description: all prose text outside the Mermaid code block — use as context for method flows, invariants, preconditions, and business rules
- Diagram: parse the Mermaid
classDiagramblock and extract:- Each class name and stereotype (
<<Aggregate Root>>,<<Entity>>,<<Value Object>>,<<Event>>(alias<<Domain Event>>),<<TypedDict>>,<<Command>>,<<Service>>(alias<<Interface>>),<<Repository>>) - Attributes with types (visibility prefix
+/-indicates public/private) - Methods with signatures
- Relationships: composition
*--, dependency-->, realization--(), including multiplicity labels and emits annotations
- Each class name and stereotype (
Step 2 — Filter classes for this category
From the diagram, collect only classes whose stereotype matches this category's mapping.
Stereotype inference for classes with no explicit stereotype:
-->with: emitsannotation →<<Event>>--()with: emitsannotation →<<Command>>
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 · 110 lines · 0 tokens per session scan A b593b58784b4
class-specifier 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 1,737 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.
.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.