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/fall-out-bug/sdp/cursorrulesgit clone --depth 1 https://github.com/fall-out-bug/sdpWhat 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.00388 | $0.00388 |
| Opus 5 | $0.00194 | $0.00194 |
| Sonnet 5 | $0.00078 | $0.00078 |
| Haiku 4.5 | $0.00039 | $0.00039 |
Grade A, and why
cursorrules 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 yesterday.
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
SDP Project Rules
This project uses Spec-Driven Protocol (SDP) v0.9.0.
Beads (SDP Development)
This repo develops SDP. Beads is ENABLED and MANDATORY here:
- Before
@build:bd update {beads_id} --status in_progress - After
@build:bd syncbefore commit - After
@design:sdp beads migrate docs/workstreams/backlog/ --real
For other projects using SDP: Beads is optional (skills check bd + .beads/).
Commands
Use skills for all work:
@vision— Strategic product planning@reality— Codebase analysis@feature— Plan feature (idea + design)@idea— Gather requirements@design— Plan workstreams@build— Execute workstream (guard enforced)@oneshot— Autonomous feature execution@review— Quality review@deploy— Production deployment
Guard Enforcement
All edits require active workstream:
sdp guard activate {PP-FFF-SS} # Before editing
sdp guard check {file} # Verify allowed
Critical Rules
Forbidden:
- Files > 200 LOC
- TODO without WS
- Edit without active WS
Required:
- TDD (Red -> Green -> Refactor)
- Coverage >= 80%
- Type hints / strict typing
- Conventional commits
Documentation
- PROTOCOL.md — Full specification
- Skills — Command details
- Quality Gates
Version: 0.9.0
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.
- yesterday First seen · 59 lines · 388 tokens per session scan A 5cf07d9beab1
cursorrules is a cursor rule published in the GitHub repository fall-out-bug/sdp (19 stars, last pushed 2mo ago), licensed MIT. It adds 388 tokens to every session, about $0.0019 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-30.
Other cursor rules, from other repositories
code-discipline
Coding methodology for production-grade software development. Enforces structured thinking before coding, verifying reality, simplicity, surgical changes, contract awareness, and verifiable success criteria. Use when writing, reviewing, or refactoring any code that must remain correct and maintainable past initial…
verificate-gate
Verificate merge gate — every substantive AI-written change must pass validateaioutput before being presented as complete.
hidden-chars
Always run the formatter before committing. Use TypeScript strict mode in every file. Prefer named exports over default exports.
style
Use descriptive variable names. Prefer small functions. Keep files under 300 lines where practical.
agent-rules
Fixture Cursor rules for agent instruction discovery.
comment-override
Follow the existing code style. Prefer small, pure functions.