Borrowing it
Nothing to install: this file belongs to leocelis/ivd. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/leocelis/ivd/main/.cursorrulesgit clone --depth 1 https://github.com/leocelis/ivdWrote 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/leocelis/ivd/cursorrules)<a href="https://agentmods.dev/rules/leocelis/ivd/cursorrules"><img src="https://agentmods.dev/badge/rules/leocelis/ivd/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.
<a href="https://agentmods.dev/rules/leocelis/ivd/cursorrules"><img src="https://agentmods.dev/badge/rules/leocelis/ivd/cursorrules.svg" alt="Reviewed on agentmods" width="80" 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.05122 | $0.05122 |
| Opus 5.5 | $0.02049 | $0.02049 |
| Sonnet 5.5 | $0.01024 | $0.01024 |
| Haiku 4.5 | $0.00512 | $0.00512 |
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.
How it starts
The opening of the file, as written. The whole thing — 425 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IVD Framework — Cursor Rules
Development rules for working on the IVD framework itself.
Both blocks below also serve as the canonical example of what
users should install in their own projects when adopting IVD.
==============================================================================
Source: leocelis/ivd/recipes/agent-rules-ivd.yaml v1.11
Reference: ivd_system_intent.yaml, framework.md, recipes/agent-rules-ivd.yaml
Do not modify by hand — reload from recipe to refresh.
==============================================================================
IVD: Intent-Verified Development Rules
==============================================================================
These rules enforce the IVD verification loop. Do not remove them.
Reference: ivd_system_intent.yaml, framework.md (Principle 4, Principle 6)
IVD Rule 1: Intent Before Implementation
Before implementing any feature, fix, or change that has an associated intent artifact (*_intent.yaml):
-
READ the intent artifact first
-
UNDERSTAND the constraints and their test paths
-
IMPLEMENT using constraint-segmented approach:
FOR INTENTS WITH 3+ CONSTRAINTS (threshold based on IFScale 2025 degradation data and Liu et al. 2023 lost-in-the-middle effect) — MANDATORY, not optional:
a. GROUP constraints into functional segments after the stress test. Example groups: input validation | core logic / output | performance | error handling | security b. IMPLEMENT one segment ONLY — do NOT single-pass the full intent c. Before implementing any constraint with conflict_prone: true, inject its anti_pattern text into the active implementation context d. RE-READ the intent constraints for that segment from disk (not from memory — forces attention reset; counters lost-in-the-middle) e. VERIFY the segment satisfies its constraints before proceeding f. Repeat steps b–e for each segment
Single-pass implementation against 3+ constraints violates Rule 1.
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 Changed · -1 lines · -11 tokens per session 924741af8647
- 2mo ago First seen · 426 lines · 5,133 tokens per session scan A 4f8111ad1a67
cursorrules is a cursor rule published in the GitHub repository leocelis/ivd (1 stars, last pushed 2d ago), licensed MIT. It adds 5,122 tokens to every session, about $0.0205 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-08-31.
cursorrules compared with cursor rules from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| cursorrulesleocelis/ivd | Cursor rule | 1 | 2d ago | MIT | A | 5,122 | Cursor |
| graphstackMertCapkin/GraphStack | Cursor rule | 8 | 4mo ago | MIT | A | 1,573 | Cursor |
| 90-devops-deploymentaiagentwithdhruv/ai-dev-stack | Cursor rule | 11 | 4mo ago | MIT | A | 0 | Cursor |
| 00-global-architectaiagentwithdhruv/ai-dev-stack | Cursor rule | 11 | 4mo ago | MIT | A | 334 | Cursor |
| 45-environment-configaiagentwithdhruv/ai-dev-stack | Cursor rule | 11 | 4mo ago | MIT | A | 302 | Cursor |
| 55-data-model-versioningaiagentwithdhruv/ai-dev-stack | Cursor rule | 11 | 4mo ago | MIT | A | 0 | Cursor |
| 85-error-observabilityaiagentwithdhruv/ai-dev-stack | Cursor rule | 11 | 4mo ago | MIT | A | 349 | Cursor |