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 Morningstar202604/awesome-skillkit --skill spec-driven-workflowgit clone --depth 1 https://github.com/Morningstar202604/awesome-skillkitWrote 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/morningstar202604/awesome-skillkit/spec-driven-workflow)<a href="https://agentmods.dev/skills/morningstar202604/awesome-skillkit/spec-driven-workflow"><img src="https://agentmods.dev/badge/skills/morningstar202604/awesome-skillkit/spec-driven-workflow/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/morningstar202604/awesome-skillkit/spec-driven-workflow"><img src="https://agentmods.dev/badge/skills/morningstar202604/awesome-skillkit/spec-driven-workflow.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.00058 | $0.02613 |
| Opus 5.5 | $0.00023 | $0.01045 |
| Sonnet 5.5 | $0.00012 | $0.00523 |
| Haiku 4.5 | $0.00006 | $0.00261 |
Grade A, and why
spec-driven-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 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-Driven Workflow
Enforces spec-first: write the spec before any code, extract test stubs from acceptance criteria after validation passes, then implement one item at a time. Every line of code traces back to a requirement in the spec.
Iron Law:
NO CODE WITHOUT AN APPROVED SPEC.
NO EXCEPTIONS. NO "QUICK PROTOTYPES." NO "I'LL DOCUMENT IT LATER."
Why spec-first: resolving ambiguity in a spec takes minutes; discovering it in production takes days; the spec is the definition of "done"; acceptance criteria translate 1:1 into test cases.
Input Checklist
| Input | Required | Description |
|---|---|---|
| Feature name and description | Yes | The seed for generating the spec template, e.g. --name "User Authentication" --description "OAuth 2.0 login flow" |
| Requirements source | Yes | User-interview notes, existing code, constraints (performance budget/security/compatibility) |
| Test framework | No | pytest / jest / go-test (test_extractor's --framework); defaults to pytest |
| Spec storage path | No | e.g. named by feature under specs/ (see delivery criteria); defaults to project convention |
| Spec status | Required at the implementation stage | Draft / In Review / Approved (no implementation before Approved) |
When inputs are missing, ask for all at once: "Please provide: (1) feature name and one-line description; (2) key requirements/constraints/explicit non-goals; (3) test framework (pytest/jest/go-test)."
Pre-flight Checks
Run line by line; on any failure → fix per the remediation and STOP:
# 1. Python 3 is available
python3 --version
# Expected: Python 3.8+.
# 2. Both tool scripts exist
ls scripts/spec_generator.py scripts/test_extractor.py
# Expected: both filenames (run inside the skill directory). On failure: cd to the skill directory; still missing → STOP and report.
# Note: this skill has no spec_validator.py — spec completeness is validated manually by the Step 3 checklist.
# 3. The reference templates are in place
ls references/spec_format_guide.md references/acceptance_criteria_patterns.md references/bounded_autonomy_rules.md
# Expected: all three filenames. Missing → STOP and report an incomplete repo.
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 Changed · -11 tokens per session 618beb7d8663
- 1mo ago Changed · -164 lines · +32 tokens per session 4ae7fe487b3a
- 1mo ago First seen · 339 lines · 37 tokens per session scan A e6ad35b6fdf6
spec-driven-workflow is a skill published in the GitHub repository Morningstar202604/awesome-skillkit (0 stars, last pushed 25d ago), licensed Apache-2.0. It adds 58 tokens to every session and 2,613 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-31.
Other skills, from other repositories
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
duckduckgo-search
Free keyless web, news, and image search via ddgs.
safe-refactor
Restructure code while preserving behavior. Use for extraction, consolidation, ownership moves, or cleanup where verification must bracket structural edits.
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
auditing-subgroup-fairness
Audit an OpenMed NER or de-identification model for performance disparities across demographic subgroups (sex, age band, race/ethnicity when available) using openmed.eval.fairnessreport. Use when the user wants per-subgroup recall and leakage, wants to check whether de-identification under-protects a group, wants to…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.