cursorrules

Project rules for Cursor, an AI coding assistant, in a freelance time-tracking project that uses spec-driven development. The approach treats the requirements, design, and task list as the project's sources of truth.

In plain words
What is it for?
Use them when Cursor changes the time-tracking project: inspect the project context and specifications, follow the next planned task, ask about ambiguity, run the required checks, and record verified completion.
Why use it?
They limit the assistant to agreed requirements and the documented data model, reducing accidental scope changes or inconsistent implementation. They also require verification before tasks are marked complete.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/fredantb/spec-driven-development/cursorrules
Clone the repo
git clone --depth 1 https://github.com/FredAntB/Spec-Driven-Development

Made for: Cursor.

Per session 430 This file is loaded in full into every session.
When invoked 430 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00430 $0.00430
Opus 5 $0.00215 $0.00215
Sonnet 5 $0.00086 $0.00086
Haiku 4.5 $0.00043 $0.00043

Measured yesterday against content hash 410e187f7ec8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

phase2c/flow_a/.cursorrules · 47 lines

What it actually says

.cursorrules

Project: Freelance Time Tracker — v1.0

═══════════════════════════════════════════════════════════ SPEC DRIVEN DEVELOPMENT — PROJECT CONSTITUTION Project: Freelance Time Tracker Version: v1.0

This project uses Spec Driven Development. All work is governed by three source-of-truth files:

requirements.md — What the system must do design.md — How the system is structured tasks.md — The ordered implementation plan

MANDATORY BEFORE ANY ACTION: 0. If CONTEXT.md exists, read it first — it has session state

  1. Read requirements.md in full
  2. Read design.md in full
  3. Read tasks.md — find the next incomplete [ ] task

HARD CONSTRAINTS:

  • Implement ONLY what is in requirements.md
  • Match EXACTLY the data model in design.md
  • Create ONLY files listed or implied by design.md
  • Never mark a task [x] without verifying its acceptance criterion
  • If a requirement is ambiguous: ASK, do not guess
  • If scope creep is detected: FLAG it, do not implement

AFTER COMPLETING A TASK:

  1. Run the verification step listed in tasks.md
  2. Mark the task [x] in tasks.md
  3. Report what was done and which REQ/NFR it satisfies

DIVERGENCE PROTOCOL: If implementation must deviate from design.md: 1. Stop immediately 2. Describe the conflict to the user 3. Wait for explicit approval to update design.md 4. Update design.md FIRST, then implement ═══════════════════════════════════════════════════════════

Cursor-Specific

  • Apply these rules to all file types in the project.
  • In Composer mode, re-read the three spec files at the start of each new Composer session.
  • Do not accept @codebase suggestions that conflict with design.md — flag the conflict instead.
Changes

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.

  1. yesterday First seen · 47 lines · 430 tokens per session scan A 410e187f7ec8

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository FredAntB/Spec-Driven-Development (152 stars, last pushed 3mo ago), licensed MIT. It adds 430 tokens to every session, about $0.0022 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.