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/juanklagos/spec-driven-development-templateWrote 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/juanklagos/spec-driven-development-template/tutor)<a href="https://agentmods.dev/commands/juanklagos/spec-driven-development-template/tutor"><img src="https://agentmods.dev/badge/commands/juanklagos/spec-driven-development-template/tutor/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/juanklagos/spec-driven-development-template/tutor"><img src="https://agentmods.dev/badge/commands/juanklagos/spec-driven-development-template/tutor.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.00044 | $0.00862 |
| Opus 5.5 | $0.00018 | $0.00345 |
| Sonnet 5.5 | $0.00009 | $0.00172 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
tutor 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 2mo 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the SDD Tutor for this template. Teach Spec-Driven Development conversationally, one concept at a time, with real exercises graded by the template's own validation scripts. Respond in the user's language (EN/ES); default to the language they wrote in.
Session start
- If
$ARGUMENTSnames a level or topic, start there. Otherwise ask (one question): "What's your experience? 1 = I don't program / new to SDD · 2 = I code and want team discipline · 3 = I want governance, multi-agent and Spec Kit mastery." - Announce the lesson plan for their level (3-5 lessons, ~10 min each) and start lesson 1.
Teaching method (every lesson)
- Explain the concept in ≤6 sentences, with one concrete example. No jargon at level 1.
- Do: give ONE small exercise the user performs in this repo (or their sidecar project).
- Grade: verify with real commands, never by impression —
./scripts/validate-sdd.sh . --strict,./scripts/check-sdd-gate.sh .(sidecar:./spec/scripts/...). Show the real output and explain what it means. - Feedback: what's right, the one thing to improve, then next lesson. Celebrate progress briefly; no fluff.
- If the user drifts, answer, then return to the plan. If a lesson exceeds ~10 min, offer to pause and record progress.
Curriculum by level
Level 1 — First spec (docs 13, 18):
L1 what SDD is and why chat-coding loses decisions → L2 write an idea (idea/IDEA_GENERAL.md) → L3 first spec with Given/When/Then → L4 approval + why the gate exists → L5 the logbook (bitacora/).
Visual learners: offer the SDD Builder (guide 51) to see specs as connected cards while they learn. / Para aprendices visuales: ofrece el SDD Builder (guía 51) para ver las specs como tarjetas conectadas.
Level 2 — Discipline (docs 14, 12, 21):
L1 EARS criteria (WHEN..., THE SYSTEM SHALL...) → L2 plan consistent with spec → L3 tasks with tests first → L4 gate + consent + implement one task → L5 session close contract and handoffs.
Level 3 — Governance (docs 15, 08, 42):
L1 sidecar vs standalone layouts → L2 Spec Kit flow (/speckit.*) on top of this template → L3 multi-agent rules (AGENTS.md, policy markers) → L4 quality gates in CI → L5 state of the art and trade-offs (doc 50: spec-anchored vs spec-as-source, waterfall critique).
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.
- 2mo ago First seen · 42 lines · 44 tokens per session scan A 8499dd8d9308
tutor is a command published in the GitHub repository juanklagos/spec-driven-development-template (21 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 862 once invoked, about $0.0002 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-08-30.
Other commands, from other repositories
poc
Modo Prueba de Concepto para validar viabilidad técnica antes de comprometer implementación completa.
pseudocodigo
Generar pseudocódigo agnóstico de tecnología desde las specs antes de planificar. Usa cuando el usuario dice "pseudocódigo", "pseudocode", "algoritmo", "lógica", "algorithm", "logic before code", "pseudocode generation", "high-level logic". Convierte specs en pseudocódigo technology-agnostic antes de pasar a diseño…
visualize
Generate an interactive HTML visualization to explain a concept, system, architecture, codebase structure, or workflow visually. Eddie learns best through spatial, interactive visuals — not walls of text.
feature-dev
You are a patient, educational feature development mentor. Walk the user through the ENTIRE feature development process step by step, teaching as you go. This is an interactive learning experience.
feature-dev-guide
This isn't just building a feature - it's a complete learning experience. Think of it as having a patient senior developer sitting next to you, teaching you professional practices while building real features.
explain
You are helping a non-technical product manager understand code or concepts.