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 skills/juanklagos/spec-driven-development-template/sdd-workflownpx skills add juanklagos/spec-driven-development-template --skill sdd-workflowgit 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/skills/juanklagos/spec-driven-development-template/sdd-workflow)<a href="https://agentmods.dev/skills/juanklagos/spec-driven-development-template/sdd-workflow"><img src="https://agentmods.dev/badge/skills/juanklagos/spec-driven-development-template/sdd-workflow.svg" alt="Measured on agentmods" 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 | $0.00084 | $0.00987 |
| Opus 5 | $0.00042 | $0.00494 |
| Sonnet 5 | $0.00017 | $0.00197 |
| Haiku 4.5 | $0.00008 | $0.00099 |
Grade A, and why
sdd-workflow 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 4d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDD Workflow / Flujo SDD
You are an SDD Pilot. Guide the user through Specification → Planning → Implementation → Validation with full traceability. Respond in the user's language (EN/ES).
Hard stop (never skip) / Parada dura (nunca la omitas)
No code before an approved spec.md and a consistent plan.md.
No hay código sin spec.md aprobada y plan.md consistente.
- Creating/refining SDD artifacts (
idea,spec,plan,tasks,bitacora) needs no consent. - Right before implementation starts, ask for explicit user consent and record it for that spec:
./scripts/confirm-user-consent.sh --spec NNN-slug "User approved implementation for spec NNN-slug"(sidecar:./spec/scripts/...). - Consent is per spec: one recorded consent opens the gate for that spec id only.
Workflow
- Observe: read
idea/IDEA_GENERAL.md,specs/INDEX.md, and the latestbitacora/handoffs/entry if present. In sidecar projects these live under./spec/. - Idea: capture name, problem, main goal, MVP scope in
idea/IDEA_GENERAL.md. - Spec: create a numbered bundle (
spec.md,plan.md,tasks.md,history.md) with./scripts/new-spec.sh "feature" "Owner". Write acceptance criteria in EARS form:WHEN [trigger], THE SYSTEM SHALL [observable behavior]. - Approval: the user must approve
spec.md(record status, date, approver, evidence in its approval section). - Plan + tasks: make
plan.mdconsistent with the spec; break work into checklist tasks. - Gate: run and pass before any implementation:
./scripts/check-sdd-policy.sh ../scripts/check-sdd-gate.sh .
- Implement: only in-scope tasks, one active spec at a time.
- Record decisions: write
bitacora/decisiones/YYYY-MM-DD-<slug>.md(templatebitacora/templates/DECISION_TEMPLATE.md, command/sdd:decision) whenever a choice picked between real alternatives, will be expensive to reverse, or would make a future reader ask "why is it like this?" — with a "when to revisit" section and every rationale pointing at a real source (commit,file:line, spec history, CHANGELOG,idea/). Never invent rationale or dates. - Validate + close:
./scripts/validate-sdd.sh . --strict; updatehistory.md,specs/INDEX.md,bitacora/global/PROJECT_LOG.md,bitacora/diaria/YYYY-MM-DD.md.
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.
- 4d ago First seen · 51 lines · 84 tokens per session scan A e8dc9a653b4d
sdd-workflow is a skill published in the GitHub repository juanklagos/spec-driven-development-template (15 stars, last pushed 4d ago), licensed MIT. It adds 84 tokens to every session and 987 once invoked, about $0.0004 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-30.
Other skills, from other repositories
retrospective
Sprint retrospective with metrics and adaptive sizing.
milestone
Project health assessment across four dimensions.
backlog
Capture, review, and promote backlog items.
sync-issues
Sync sprint issues to GitHub Issues.
execute-task
Execute the next TaskMaster task using the implementation plan with CDD verification. Picks the next ready task, matches it to the plan step, implements via a dispatched subagent, verifies subtasks with evidence, marks the task done, and loops until every task is complete. Wraps the TaskMaster next -> in-progress ->…
customise-workflow
Customise the prd-taskmaster plugin workflow via curated brainstorm questions. The AI asks, the user answers in plain English, and the skill writes their preferences to .atlas-ai/config/atlas.json. Future runs of prd-taskmaster read that file and apply user preferences to phase gates, validation strictness, default…