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 skills add liatrio-labs/spec-driven-workflow --skill skillgit clone --depth 1 https://github.com/liatrio-labs/spec-driven-workflowWrote 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/liatrio-labs/spec-driven-workflow/skill)<a href="https://agentmods.dev/skills/liatrio-labs/spec-driven-workflow/skill"><img src="https://agentmods.dev/badge/skills/liatrio-labs/spec-driven-workflow/skill/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/skills/liatrio-labs/spec-driven-workflow/skill"><img src="https://agentmods.dev/badge/skills/liatrio-labs/spec-driven-workflow/skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00050 | $0.01345 |
| Opus 5.5 | $0.00020 | $0.00538 |
| Sonnet 5.5 | $0.00010 | $0.00269 |
| Haiku 4.5 | $0.00005 | $0.00135 |
Grade A, and why
sdd 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-Driven Workflow Orchestrator
You are the orchestrator for the Spec-Driven Development (SDD) workflow. Determine the current lifecycle phase from the workspace, then load and follow the single matching phase reference.
Skill Contract
This skill manages one SDD phase per invocation unless the loaded phase explicitly requires a smaller checkpoint. It must:
- Assess workspace state before routing.
- Select exactly one active spec and one phase reference.
- Load only that phase reference.
- Execute the phase instructions or stop at a required approval gate.
- Tell the user the selected spec, detected state, current phase, chosen phase reference path, created or updated artifacts, and next recommended natural-language request.
If multiple active specs exist and the user request does not clearly identify one, ask the user which spec to continue before modifying files. If the selection is unambiguous, state why that spec was selected.
State Assessment
Before routing, run the bundled assessor script while the current working directory is the target repository/workspace root:
python3 {{skill_dir}}/scripts/assess-sdd-state.py .
{{skill_dir}} locates bundled skill assets only; SDD artifacts are assessed from the workspace path argument (. in the command above). The script outputs JSON describing active specs and a recommended phase. Use that output as the default source of truth for routing.
Use manual inspection only if the script cannot run. When falling back manually, state that fallback explicitly, inspect ./docs/specs/, and apply the same phase rules below.
Phase Rules
-
Phase 1 — Spec Generation
- Condition: The user requested a new feature, but no matching
[NN]-spec-[feature-name]/directory exists, or the spec directory exists but the spec document is incomplete or missing. - Action: Gather context and write the formal specification.
- Condition: The user requested a new feature, but no matching
-
Phase 2 — Task List Generation and Audit
- Condition:
[NN]-spec-[feature-name].mdexists and is complete, but[NN]-tasks-[feature-name].mdis missing, or the mandatory[NN]-audit-[feature-name].mdplanning audit has not been generated and passed. - Action: Translate the spec into parent/sub-tasks, define Proof Artifacts, and run the mandatory planning audit gate.
- Condition:
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 105 lines · 50 tokens per session scan A eb99d52b096a
sdd is a skill published in the GitHub repository liatrio-labs/spec-driven-workflow (95 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 50 tokens to every session and 1,345 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 skills, from other repositories
michel-run-local-dev-stack
The canonical recipe for starting, checking, and stopping the Packmind local dev stack with Docker Compose — the single source of truth other skills and the Michel agent defer to. Covers bringing the full stack (PostgreSQL, Redis, NestJS API, React/Vite frontend on :4200, MCP server, nginx) up in the background, the…
michel-cli-demo-recorder
Produce proof-of-execution demos of the Packmind CLI (packmind-cli) as terminal-styled images (colors and formatting preserved exactly), for embedding in a GitHub PR. Renders a crisp master SVG and rasterizes it to a PNG — the PNG is what you embed, because GitHub does not render SVG in PR/issue bodies. Use this…
hexagonal-architecture
Describes the hexagonal architecture (ports and adapters) used across the Packmind monorepo. This skill should be used when creating new domain packages, use cases, services, repositories, domain error classes, or any architectural component to follow established patterns, including how a failure raised in a use case…
michel-create-packmind-dataset
Seed a local Packmind instance with a realistic dataset — one organization populated with standards, commands, and skills — so an autonomous agent can exercise its own changes against lifelike data instead of an empty app. Use this whenever you need populated Packmind data to verify a change end-to-end: reproducing a…
dsh-plugin-publisher
A release tool for DSH plugins, where DSH is the DeepSeek Harness used to load these add-ons. It validates an existing plugin package, publishes it through npm, Git, or a tarball, and checks that the harness can load it.
lov-publish-event-onto-hdx
A tool for diagnosing how an event appears on Huodongxing, a Chinese event-listing website. It checks the event’s category, tags, visibility, and ranking.