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/commands/voro6yov/spec-driven-development/template)<a href="https://agentmods.dev/commands/voro6yov/spec-driven-development/template"><img src="https://agentmods.dev/badge/commands/voro6yov/spec-driven-development/template/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/commands/voro6yov/spec-driven-development/template"><img src="https://agentmods.dev/badge/commands/voro6yov/spec-driven-development/template.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.00000 | $0.00921 |
| Opus 5.5 | $0.00000 | $0.00368 |
| Sonnet 5.5 | $0.00000 | $0.00184 |
| Haiku 4.5 | $0.00000 | $0.00092 |
Grade A, and why
template 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 1mo 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commands Template
from dataclasses import dataclass
from typing import ClassVar
from ..shared import Command, CommandReply
__all__ = ["{{ command_name }}", "{{ success_reply_name }}", "{{ failure_reply_name }}"]
@dataclass
class {{ command_name }}(Command):
COMMAND_CHANNEL: ClassVar[str] = "{{ command_channel }}"
REPLY_CHANNEL: ClassVar[str] = "{{ reply_channel }}"
{{ correlation_field_1 }}: str
{{ correlation_field_2 }}: str
{{ aggregate_id }}: str
{{ input_field_1 }}: {{ input_type_1 }}
@dataclass
class {{ success_reply_name }}(CommandReply):
{{ correlation_field_1 }}: str
{{ correlation_field_2 }}: str
{{ aggregate_id }}: str
{{ result_field_1 }}: {{ result_type_1 }}
{{ result_field_2 }}: {{ result_type_2 }} | None
@dataclass
class {{ failure_reply_name }}(CommandReply):
{{ correlation_field_1 }}: str
{{ correlation_field_2 }}: str
{{ aggregate_id }}: str
error_message: str
Placeholders — Command
| Placeholder | Description | Example |
|---|---|---|
{{ command_name }} |
Imperative verb name | StartLabelProcessing, ProcessSidewallImage |
{{ command_channel }} |
Channel for command routing | LabelProcessing, SidewallProcessing |
{{ reply_channel }} |
Channel for reply routing | TireIdentificationReplies, DocumentReplies |
{{ correlation_field_1 }} |
First correlation identifier | conveyor_id, session_id |
{{ correlation_field_2 }} |
Second correlation identifier | warehouse_id, tenant_id |
{{ aggregate_id }} |
ID of target aggregate | tire_id, document_id |
{{ input_field_1 }} |
Input data for processing | label_text, image_path |
{{ input_type_1 }} |
Type of input data | str, bytes, dict[str, str] |
Placeholders — Success Reply
| Placeholder | Description | Example |
|---|---|---|
{{ success_reply_name }} |
Success reply class name | LabelProcessingSuccess, SidewallProcessingSuccess |
{{ result_field_1 }} |
Primary result field | extracted_product_name, classification_result |
{{ result_type_1 }} |
Type of primary result | ExtractedProductName, ClassificationResult |
{{ result_field_2 }} |
Secondary result field | processing_time, confidence_score |
{{ result_type_2 }} |
Type of secondary result | float, dict[str, float] |
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.
- 1mo ago First seen · 115 lines · 0 tokens per session scan A 48a138e16703
template is a command published in the GitHub repository voro6yov/spec-driven-development (5 stars, last pushed 13d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 921 tokens. 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 commands, from other repositories
type-coverage
Vérification Couverture des Types Python.
execute-pydantic-ai-prp
Implement a Pydantic AI agent using the PRP file.
package-review
Review the current Python package for best-practice violations — project structure, pyproject.toml, typing, testing, CI/CD, documentation, versioning, API design, packaging, security, and developer experience.
fastapi
FastAPI application design and implementation conventions. Use this skill when building, updating, or reviewing FastAPI services, routers, dependencies, request/response schemas, streaming endpoints, or API tests. Trigger on FastAPI-specific work such as path operation design, dependency injection, response models…
savant-python
Python performance optimization with Python Developer agent.
python-review
Comprehensive Python code review for PEP 8 compliance, type hints, security, and Pythonic idioms. Invokes the python-reviewer agent.