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.
git clone --depth 1 https://github.com/elirancv/CursorMDWrote 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/elirancv/cursormd/document-dependencies)<a href="https://agentmods.dev/rules/elirancv/cursormd/document-dependencies"><img src="https://agentmods.dev/badge/rules/elirancv/cursormd/document-dependencies/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/elirancv/cursormd/document-dependencies"><img src="https://agentmods.dev/badge/rules/elirancv/cursormd/document-dependencies.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.03614 | $0.03614 |
| Opus 5.5 | $0.01446 | $0.01446 |
| Sonnet 5.5 | $0.00723 | $0.00723 |
| Haiku 4.5 | $0.00361 | $0.00361 |
Grade A, and why
document-dependencies 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 408 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Document Dependencies & Auto-Detection
Core Principle: Documentation as a Puzzle
"Proper specification is 50% of the work" - Once the specification is perfect, building the project becomes easier - it's like a puzzle. Documents must be built in the correct order, with each piece depending on previous ones.
Auto-Detection System
When User Starts or Asks "What's Missing?"
Automatically:
- Scan project for existing documentation files
- Identify missing critical documents based on project stage
- Detect dependencies - what needs to be created first
- Suggest build order - the correct sequence (like puzzle pieces)
- Track progress - show what's done, what's missing, what's next
Document Dependency Graph
Documents have dependencies - some must be created before others:
Foundation Layer (Start Here)
VISION.md
↓
PROBLEM_STATEMENT.md
↓
PRODUCT_OVERVIEW.md
Requirements Layer (Depends on Foundation)
VISION.md → PRD_MVP.md
PROBLEM_STATEMENT.md → USER_STORIES.md
PRODUCT_OVERVIEW.md → SCOPE_DOCUMENT.md
Architecture Layer (Depends on Requirements)
PRD_MVP.md → ARCHITECTURE_OVERVIEW.md
USER_STORIES.md → TECH_SPEC_MVP.md
SCOPE_DOCUMENT.md → SYSTEM_COMPONENTS.md
Implementation Layer (Depends on Architecture)
ARCHITECTURE_OVERVIEW.md → ENGINEERING_GUIDE.md
TECH_SPEC_MVP.md → PIPELINE_MVP.md
SYSTEM_COMPONENTS.md → DATA_MODEL.md
Operations Layer (Depends on Implementation)
ENGINEERING_GUIDE.md → DEPLOYMENT_RUNBOOK.md
PIPELINE_MVP.md → CI_CD_PIPELINE.md
DATA_MODEL.md → INFRASTRUCTURE_OVERVIEW.md
Complete Dependency Map
Level 1 - Foundation (No dependencies):
- VISION.md
- PROBLEM_STATEMENT.md
- MARKET_ANALYSIS.md
- ONE_PAGER.md
Level 2 - Strategy (Depends on Level 1):
- PRODUCT_OVERVIEW.md (needs: VISION.md)
- VALUE_PROPOSITION.md (needs: PROBLEM_STATEMENT.md, MARKET_ANALYSIS.md)
- POSITIONING.md (needs: MARKET_ANALYSIS.md)
- USE_CASES.md (needs: PROBLEM_STATEMENT.md)
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.
- 1mo ago First seen · 408 lines · 3,614 tokens per session scan A 12d5e941300a
document-dependencies is a cursor rule published in the GitHub repository elirancv/CursorMD (1 stars, last pushed 11mo ago), licensed MIT. It adds 3,614 tokens to every session, about $0.0145 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.
Other cursor rules, from other repositories
documentation
Documentation: code docs, READMEs, ADRs, maintenance.
react-formengine-ai-form-builder-cursorrules-prompt-file
Cursor rules for generating React forms from screenshots, PDFs, HTML, or text descriptions with validated FormEngine JSON schema. Renders through RSuite, Material UI, or Mantine.
readme-best-practices-cursorrules-prompt-file
Cursor rules for README documentation with best practices integration.
refactoring
Refactoring: systematic approach, extract/inline, guard clauses, early returns.
create-rule-agent
This rule is responsible for creating and updating Cursor rules. Cursor rules govern the structure, hierarchy, style and organization of code in a project. This rule should be invoked in Agent mode when: 1. a user wants to create a new cursor rule, 2. a user wants to update or change an existing rule, 3. user wants…
cloudflare-workers-hono-auto
Cloudflare Workers with Hono framework development standards and best practices.