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/marcusgoll/spec-flow/cursorrulesgit clone --depth 1 https://github.com/marcusgoll/Spec-FlowWrote 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/marcusgoll/spec-flow/cursorrules)<a href="https://agentmods.dev/rules/marcusgoll/spec-flow/cursorrules"><img src="https://agentmods.dev/badge/rules/marcusgoll/spec-flow/cursorrules.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 | $0.00112 | $0.00112 |
| Opus 5 | $0.00056 | $0.00056 |
| Sonnet 5 | $0.00022 | $0.00022 |
| Haiku 4.5 | $0.00011 | $0.00011 |
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
Spec-Flow + Cursor ground rules
- Shared canon lives in
.spec-flow/(repo map, domain guides, state schemas) andepics/<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.yamland stop at manual gates before editing subsequent phases.
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 · 7 lines · 112 tokens per session scan A 60ae6216d4ea
cursorrules is a cursor rule published in the GitHub repository marcusgoll/Spec-Flow (92 stars, last pushed 4mo ago), licensed MIT. It adds 112 tokens to every session, about $0.0006 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-09-03.
Other cursor rules, from other repositories
orchestrate
Apply the Workflow Orchestration methodology for complex, multi-step tasks — plan-first approach, subagent strategy, self-improvement loo...
update-claude-md
After any correction from the user, update CLAUDE.md with a rule to prevent the same mistake from recurring.
skill-selection
Pick the fewest skills for this task. Core lifecycle for non-trivial work; extras only on a matching signal. Catalog is using-agent-skills, not this rule.
infra-devops
Infrastructure, Cloud, Terraform, Docker & CI/CD Agent.
context-delegate
Context Gatherer & External LLM Prompt Generator.
cis-innovation-oracle
CIS Agent — Victor (Disruptive Innovation Oracle).