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/jmanhype/speckit/spec-kit-workflownpx skills add jmanhype/speckit --skill spec-kit-workflowgit clone --depth 1 https://github.com/jmanhype/speckitWrote 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/jmanhype/speckit/spec-kit-workflow)<a href="https://agentmods.dev/skills/jmanhype/speckit/spec-kit-workflow"><img src="https://agentmods.dev/badge/skills/jmanhype/speckit/spec-kit-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.1 | $0.00049 | $0.00907 |
| Opus 5 | $0.00024 | $0.00453 |
| Sonnet 5 | $0.00010 | $0.00181 |
| Haiku 4.5 | $0.00005 | $0.00091 |
Grade A, and why
spec-kit-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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Kit Workflow Skill
You are assisting with a project that uses Spec Kit - a specification-driven development framework. This skill ensures proper workflow adherence.
Workflow Phases
The Spec Kit workflow follows this progression:
constitution → specify → clarify → plan → checklist → tasks → analyze → implement
Phase Descriptions
-
Constitution (
/speckit.constitution)- Define project-level architectural principles
- Stored in
.specify/memory/constitution.md - One-time setup per project
-
Specify (
/speckit.specify <description>)- Create user-focused specification (WHAT/WHY)
- Technology-agnostic requirements
- Creates
specs/###-feature-name/spec.md
-
Clarify (
/speckit.clarify)- Resolve ambiguities in the spec
- Maximum 3 high-impact questions
- Updates spec.md with answers
-
Plan (
/speckit.plan)- Create technical implementation plan (HOW)
- Architecture, dependencies, file structure
- Creates
plan.mdin feature directory
-
Checklist (
/speckit.checklist)- Generate domain-specific quality checklists
- Security, accessibility, performance
- Creates
checklists/in feature directory
-
Tasks (
/speckit.tasks)- Generate executable, dependency-ordered tasks
- Includes file paths, user story references
- Creates
tasks.mdin feature directory
-
Analyze (
/speckit.analyze)- Cross-artifact consistency validation
- Ensures spec → plan → tasks alignment
- CRITICAL: Run before implementation
-
Implement (
/speckit.implement)- Execute tasks following dependencies
- Run tests for each completed task
- Update task status in tasks.md
When to Invoke This Skill
Claude should use this skill when the user:
- Mentions adding a new feature
- Discusses specifications or requirements
- Asks about planning implementation
- Wants to understand the development workflow
- References spec.md, plan.md, or tasks.md files
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 · 124 lines · 49 tokens per session scan A fe7583a4393d
spec-kit-workflow is a skill published in the GitHub repository jmanhype/speckit (26 stars, last pushed 5mo ago), licensed MIT. It adds 49 tokens to every session and 907 once invoked, about $0.0002 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
scaffold-runner
Interactive wrapper for the scaffold CLI that surfaces a pipeline step's decision points before executing it and manages the step lifecycle. Use when the user asks to run a scaffold step ("run scaffold ", "scaffold ", "what's next?"), to start building, or works in a project with a .scaffold/ directory.
work-beads
Work the project's Beads task queue end-to-end - claim a bead, build in an isolated worktree, verify, review, merge, close, report. Use when the user says "/work-beads", "/work-beads 5", "work the next N beads", "work on ", "pick up some open tasks", or asks to work the backlog. Applies to every coding agent (Claude…
scaffold-pipeline
Static reference for scaffold pipeline ordering, dependencies, and phase structure. Use ONLY for questions about pipeline design, step ordering, or dependency constraints — NOT for status, progress, or "what's next" queries (those go through scaffold-runner).
multi-model-dispatch
Correct patterns for invoking Codex CLI and Antigravity CLI (agy) as independent reviewers from Claude Code. Covers headless invocation, context bundling, output parsing, dual-model reconciliation, and fallback handling.
mmr
Run multi-model code review with the MMR CLI (mmr review) before merging or finishing a change, or a multi-model design critique (mmr critique) of a design doc, plan, or proposed approach before building it. Use when the user asks to review code, a PR, a diff, or staged changes, or to critique/second-opinion a design…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…