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/attilaszasz/sdd-pilotWrote 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/attilaszasz/sdd-pilot/sddp-specs)<a href="https://agentmods.dev/rules/attilaszasz/sdd-pilot/sddp-specs"><img src="https://agentmods.dev/badge/rules/attilaszasz/sdd-pilot/sddp-specs.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.00000 | $0.00853 |
| Opus 5 | $0.00000 | $0.00426 |
| Sonnet 5 | $0.00000 | $0.00171 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
sddp-specs 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 2d 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDD Pilot — Specification File Conventions
When editing feature-artifact files inside a Feature Workspace at specs/<feature-folder>/, follow these rules. Standalone ADR files under specs/adrs/ also use the ADR preservation rules listed below. Do not apply these rules to other Project Context Specs such as specs/prd.md, specs/sad.md, specs/dod.md, or specs/project-plan.md.
For the full rule set, see .github/skills/artifact-conventions/SKILL.md.
Preservation Rules
- Treat missing
spec_typeinspec.mdfrontmatter asproduct - Do NOT reorder product user story priorities or non-product objective priorities (P1, P2, P3) without explicit user approval
- Do NOT change task IDs (T001, T002...) — they are used for cross-referencing
- Do NOT change checklist IDs (CHK001, CHK002...) — they are referenced externally
- Do NOT change requirement IDs (FR-001, TR-001, OR-001, RR-001) — they are mapped to tasks and coverage reports
- Do NOT change success criteria IDs (SC-001, SC-002...) — they are referenced in phase reviews
- Do NOT change architecture decision IDs (AD-001, AD-002...) — they may be referenced by tasks
- Do NOT rename, renumber, or delete standalone ADR files under
specs/adrs/— ADR-NNNN numbers are monotonic, never reused, and cross-referenced by project-plan epics, traceability tags{SAD:ADR-NNNN}, and the sad.md catalog - Do NOT write standalone ADR files outside the ADR Author subagent (
.github/agents/_adr-author.md) - Preserve checkbox state (
- [ ]vs- [X]) — changing state has gating consequences - The only valid checkbox transition is
- [ ]→- [X](completed). Never reverse without explicit user approval. - Respect
[NEEDS CLARIFICATION]markers — only resolve with user-approved answers
Format Rules
- Task format:
- [ ] T### [P?] [US#|OBJ#?] {(FR|TR|OR|RR)-###?} Description with file path - Requirement format:
(FR|TR|OR|RR)-###: ... - Success criteria format:
SC-### [US#|OBJ#]: [Measurable, technology-agnostic outcome] - Checklist format:
- [ ] CHK### <question> [Quality Dimension, Spec §X.Y]
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.
- 2d ago First seen · 41 lines · 0 tokens per session scan A 1c0edce872e5
sddp-specs is a cursor rule published in the GitHub repository attilaszasz/sdd-pilot (95 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 853 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-06.
Other cursor rules, from other repositories
vibeflow
Vibeflow spec-driven development methodology — guardrails, pipeline, and project knowledge system.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.