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.
git clone --depth 1 https://github.com/Hundia/autospecWrote 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/hundia/autospec/sdd-workflow)<a href="https://agentmods.dev/rules/hundia/autospec/sdd-workflow"><img src="https://agentmods.dev/badge/rules/hundia/autospec/sdd-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/rules/hundia/autospec/sdd-workflow"><img src="https://agentmods.dev/badge/rules/hundia/autospec/sdd-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.00000 | $0.00822 |
| Opus 5.5 | $0.00000 | $0.00329 |
| Sonnet 5.5 | $0.00000 | $0.00164 |
| Haiku 4.5 | $0.00000 | $0.00082 |
Grade A, and why
sdd-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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDD Workflow Rules
This project uses Spec-Driven Development (SDD) — specs and docs are the source of truth, code follows.
Key Files
| File | Purpose |
|---|---|
specs/backlog.md |
Sprint backlog — all tickets, statuses, priorities |
specs/01-project-overview.md |
Project vision, goals, constraints |
specs/02-roles.md |
Role definitions (PM, Architect, Dev, QA) |
specs/03-user-stories.md |
User stories and acceptance criteria |
specs/04-architecture.md |
System architecture and patterns |
specs/05-data-models.md |
Data models and schemas |
specs/06-api-surface.md |
API endpoints and contracts |
specs/10-sdd-methodology.md |
SDD methodology reference |
Backlog-First Development
Every fix, feature, or change MUST be tracked in specs/backlog.md:
- Check if a ticket already exists for the work
- If not, add one with the correct format (see
update-backlog.mdc) - Set status to 🔄 In Progress when starting
- Set status to ✅ Done when complete
Status Emojis
- 🔲 Not started
- 🔄 In progress
- 🧪 In QA / testing
- ✅ Done
- ⏸️ Blocked / paused
Docs-First Rule
Before modifying any code:
- Read relevant
docs/files for the subsystem you are changing - Read the relevant spec file (
specs/02-06,specs/10) - Implement the change
- Update
docs/to reflect your changes (living documentation)
Documentation directories:
docs/viewer/— Viewer app (React)docs/cli/— CLI tool (Node/TypeScript)docs/methodology/— SDD philosophy and patternsdocs/deployment/— CI/CD and GitHub Pagesdocs/environments/— IDE and terminal setup
Code Conventions
- TypeScript with strict mode enabled
- Zod for runtime validation and schema definitions
- Architecture: repository → service → controller layering
- Frontend: React + Tailwind CSS + Zustand for state
- Testing: Vitest for unit/integration tests
Commit Format
type(scope): description
Types: feat, fix, docs, refactor, test, chore, style
Scopes: cli, viewer, specs, docs, skills, agents
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 · 100 lines · 0 tokens per session scan A 354c65a8e2b1
sdd-workflow is a cursor rule published in the GitHub repository Hundia/autospec (4 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 822 tokens. 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-03.
Other cursor rules, from other repositories
slice-tasks
PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
elite-orchestrator
Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
linear-in-review
After finishing a Linear issue, set its status to In Review (never Done).
sprint-planning
BMAD BMM Agent: sprint-planning.