A set of rules for turning product ideas into software through structured, specification-led steps. It uses shared project documents, quality checks, and tracked workflow state.

It guides work on product features and epics, including specification, clarification, planning, implementation, optimization, preview, and release.

It gives teams a repeatable process and makes phase progress and decisions easier to audit.

How marcusgoll/Spec-Flow configures Cursor

Reuse

Borrowing it

Nothing to install: this file belongs to marcusgoll/Spec-Flow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/marcusgoll/Spec-Flow/main/.cursorrules

Clone the repo

git clone --depth 1 https://github.com/marcusgoll/Spec-Flow

Made for: Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/marcusgoll/spec-flow/cursorrules/github.svg)](https://agentmods.dev/rules/marcusgoll/spec-flow/cursorrules)

Your own site

<a href="https://agentmods.dev/rules/marcusgoll/spec-flow/cursorrules"><img src="https://agentmods.dev/badge/rules/marcusgoll/spec-flow/cursorrules/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/marcusgoll/spec-flow/cursorrules"><img src="https://agentmods.dev/badge/rules/marcusgoll/spec-flow/cursorrules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 112 This file is loaded in full into every session.

When invoked 112 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00112	$0.00112
Opus 5.5	$0.00045	$0.00045
Sonnet 5.5	$0.00022	$0.00022
Haiku 4.5	$0.00011	$0.00011

Measured 2mo ago against content hash 60ae6216d4ea, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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.

.cursorrules · 7 lines

What it actually says

Spec-Flow + Cursor ground rules

Shared canon lives in .spec-flow/ (repo map, domain guides, state schemas) and epics/<slug>/state.yaml.
.claude/ is read-only for Cursor; use it only as reference for how phases should behave.
Cursor-specific prompts/adapters belong in .cursor/.
Run only one epic phase per session unless explicitly told to chain spec → clarify → plan.
Always update the relevant state.yaml and stop at manual gates before editing subsequent phases.

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.

2mo ago First seen · 7 lines · 112 tokens per session scan A 60ae6216d4ea

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository marcusgoll/Spec-Flow (96 stars, last pushed 1mo ago), licensed MIT. It adds 112 tokens to every session, about $0.0004 per session on Opus 5.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-09-03.

Planning Project management ai-agents ai-assisted-development ai-workflows automation bash claude

cursorrules next to 6 cursor rules from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
cursorrulesmarcusgoll/Spec-Flow	Cursor rule	96	1mo ago	MIT	A	112	Cursor
orchestraterajitsaha/100xprism	Cursor rule	10	9d ago	MIT	A	27	Cursor
update-claude-mdrajitsaha/100xprism	Cursor rule	10	9d ago	MIT	A	22	Cursor
infra-devopsPlanVault/ai-engineering-playbook	Cursor rule	6	2mo ago	none	A	0	Cursor
cis-innovation-oraclebogdaniel/aegis-codex	Cursor rule	3	11mo ago	MIT	A	0	Cursor
refactorerbogdaniel/aegis-codex	Cursor rule	3	11mo ago	MIT	A	0	Cursor
nextjsdevridge0/basilic-evm	Cursor rule	5	1y ago	WTFPL	A	807	Cursor

Spec-Flow: Cursor rule for Cursor