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 rules/enovatr-labs/specroute/spec-driven-workflowgit clone --depth 1 https://github.com/Enovatr-Labs/SpecRouteWrote 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/rules/enovatr-labs/specroute/spec-driven-workflow)<a href="https://agentmods.dev/rules/enovatr-labs/specroute/spec-driven-workflow"><img src="https://agentmods.dev/badge/rules/enovatr-labs/specroute/spec-driven-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.00189 | $0.00189 |
| Opus 5 | $0.00095 | $0.00095 |
| Sonnet 5 | $0.00038 | $0.00038 |
| Haiku 4.5 | $0.00019 | $0.00019 |
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 5d 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 Workflow
Use this rule in every Cursor conversation for a SpecRoute-enabled repo.
Canonical Flow
Work moves in this order:
PRD -> requirements/design/tasks -> implementation -> validation -> review
Do not skip from a vague request directly to implementation when the change needs product scope, interface design, rollout planning, or acceptance criteria.
Artifact Routing
- Put product intent and success metrics in
prds/. - Put requirements, design, and implementation tasks in
specs/. - Put reusable prompts in
prompts/. - Put engineering rules in
rules/. - Put runtime-specific Cursor rules in
.cursor/rules/.
Review Standard
Before implementation starts, verify that the active spec has stable requirement IDs, clear acceptance criteria, and tasks that reference the requirements they satisfy.
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.
- 5d ago First seen · 31 lines · 189 tokens per session scan A d8b1dfbcc78b
spec-driven-workflow is a cursor rule published in the GitHub repository Enovatr-Labs/SpecRoute (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 189 tokens to every session, about $0.0009 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-31.
Other cursor rules, from other repositories
050-plan
When the user types /plan or asks to create a project plan, feature PRD, or retrospective.
cursor-tools-mastery
Cursor 3.7 runtime guide: choose the right tool, canvases, Design Mode, /worktree, /best-of-n, Await, and parallel execution where safe.
cursor-agent-orchestration
Cursor 3.7 orchestration guide: when to plan, when to delegate, nested subagents, multi-environment handoffs, /best-of-n, and Await for long-running branches.
cursor-mcp-optimization
Cursor 3.7 MCP optimization: browser Design Mode, canvases, Figma, Cloudflare tools, MCP Apps structured content, and direct action patterns.
aria-audit
ARIA audit skills — /audit dispatcher plus /audit-knowledge, /audit-config, /audit-style, /audit-usage. Use when user says 'audit knowledge', 'audit config', 'audit style', 'audit usage', 'review setup', or runs the slash commands.
agents-api
⚠️ MVP Context: This is an active proof-of-concept for "vibe coding" with no production users yet. Some features may be partially implemented or evolving.