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 Plazmodium/odin-workflow --skill spec-driven-developmentgit clone --depth 1 https://github.com/Plazmodium/odin-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/plazmodium/odin-workflow/spec-driven-development)<a href="https://agentmods.dev/skills/plazmodium/odin-workflow/spec-driven-development"><img src="https://agentmods.dev/badge/skills/plazmodium/odin-workflow/spec-driven-development.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.1 | $0.00020 | $0.00336 |
| Opus 5 | $0.00010 | $0.00168 |
| Sonnet 5 | $0.00004 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
spec-driven-development 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 6d 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.
What it actually says
spec-driven-development
When To Use
- Starting a feature, project, API, migration, or significant behavior change.
- The work crosses files, teams, trust boundaries, or user-visible behavior.
- The user asks for a spec, PRD, or design before implementation.
Workflow
- State the goal and why it matters.
- Define in-scope and out-of-scope work.
- Capture assumptions and unresolved questions.
- Write acceptance criteria as observable outcomes.
- Describe user-visible behavior and failure behavior.
- Identify affected files, APIs, data, dependencies, and trust boundaries.
- Define the verification plan before coding.
- Stop if acceptance criteria or boundaries are materially unclear.
Anti-Rationalization
| Excuse | Rebuttal |
|---|---|
| "This task is too simple for a spec." | Acceptance criteria can be five lines. Zero lines is the problem. |
| "The code will clarify the requirements." | Code written before requirements tends to encode guesses. |
| "The user already knows what they want." | The agent must know what is being optimized and what is excluded. |
Verification
- Spec includes goal, scope, non-goals, assumptions, acceptance criteria, and verification.
- Ambiguities that affect implementation are resolved or explicitly deferred.
- The verification plan can produce concrete evidence.
Exit Criteria
- A reviewer can tell what success means without reading the implementation.
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.
- 6d ago First seen · 44 lines · 20 tokens per session scan A a7e0e9e0cc58
spec-driven-development is a skill published in the GitHub repository Plazmodium/odin-workflow (0 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 336 once invoked, about $0.0001 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-09-01.
Other skills, from other repositories
b123d-modeling
Use this skill when asked to model, build, or modify a 3D part or assembly with build123d — from a text description, a technical drawing (image or PDF), dimensions in a spec, or an existing STEP/STL file.
b123d-edit
Use this skill when the task is to change an existing build123d model or script: "make this bracket 5 mm taller", "move the holes inward", "add a counterbore", "remove this rib", "make it fit this mating part", or "repair the code so the intended edit remains parametric".
new-gh-issue-orchestration
Orchestrates a GitHub-issue-driven delivery workflow from issue intake to PR creation using reviewer-first then worker execution. Invoked when the user provides a GitHub issue link/number and asks to start end-to-end delivery.
hmem-release
Pre-publish checklist for hmem: skills synced, version bumped, tests green, nothing forgotten. Use before npm publish or when the user says 'release', 'publish', 'push a release', or 'neue Version'.
mlflow-traces
Use when working with MLflow traces: debugging via MCP tools, analyzing performance, logging feedback, writing custom scorers/evaluations, or cleaning up trace data.
video-explainer
Teaches Claude how to use the 15 video explainer tools to create explainer videos from research content. Activates when working with video synthesis, explainer creation, or the video-explainer MCP server.