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-types)<a href="https://agentmods.dev/rules/elirancv/cursormd/document-types"><img src="https://agentmods.dev/badge/rules/elirancv/cursormd/document-types/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-types"><img src="https://agentmods.dev/badge/rules/elirancv/cursormd/document-types.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.00944 | $0.00944 |
| Opus 5.5 | $0.00378 | $0.00378 |
| Sonnet 5.5 | $0.00189 | $0.00189 |
| Haiku 4.5 | $0.00094 | $0.00094 |
Grade A, and why
document-types 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Document Types Catalog
You have access to a comprehensive catalog of 53 document types covering all aspects of SaaS/Platform projects from idea to production (42 core types + 11 additional engineering and operational documents).
Document Categories
1. Vision & Strategy (8 types)
- VISION.md
- PRODUCT_OVERVIEW.md
- ONE_PAGER.md
- PROBLEM_STATEMENT.md
- MARKET_ANALYSIS.md
- POSITIONING.md
- VALUE_PROPOSITION.md
- USE_CASES.md
2. Product Requirements (6 types)
- PRD_MVP.md
- PRD_V1.md
- SCOPE_DOCUMENT.md
- USER_STORIES.md
- ACCEPTANCE_CRITERIA.md
- PRODUCT_FEATURE_LIST.md
3. Architecture & System Design (13 types)
- ARCHITECTURE_OVERVIEW.md
- SYSTEM_COMPONENTS.md
- SYSTEM_DIAGRAMS.md
- TECH_SPEC_MVP.md (12 sections)
- TECH_SPEC_V1_ENTERPRISE.md
- ORCHESTRATOR_SPEC.md
- AGENT_CONTRACT_SPEC.md
- ADVISOR_CONTRACT_SPEC.md
- QUALITY_GATE_SPEC.md
- POLICY_ENGINE_SPEC.md
- DATA_MODEL.md
- ARTIFACT_MODEL.md
- EVENTLOG_SCHEMA.md
- MANIFEST_SCHEMA.md
4. Execution & Pipelines (5 types)
- PIPELINE_MVP.md
- PIPELINE_V1.md
- EXECUTION_MODEL.md
- RETRY_AND_RESUME_LOGIC.md
- FAILURE_MODES.md
5. Engineering & Implementation (13 types)
- ENGINEERING_GUIDE.md
- CODING_STANDARDS.md
- CONTRIBUTING.md
- TEST_PLAN.md
- SMOKE_TEST_SUITE.md
- LLM_EVALUATION_TESTS.md
- DEPLOYMENT_RUNBOOK.md
- INFRASTRUCTURE_OVERVIEW.md
- CI_CD_PIPELINE.md
- OBSERVABILITY.md
- API_CONTRACT.md
- EDGE_CASES.md
- SCALABILITY_PLAN.md
6. Governance, Policy & Enterprise (6 types)
- QUALITY_MANAGEMENT_POLICY.md
- POLICY_DEFINITION_GUIDE.md
- COUNCIL_DESIGN.md
- SECURITY_GUIDELINES.md
- DATA_PRIVACY.md
- ACCESS_CONTROL_ARCHITECTURE.md
7. Business & Financial (6 types)
- BUSINESS_MODEL.md
- PRICING_STRATEGY.md
- GO_TO_MARKET_PLAN.md
- COST_STRUCTURE.md
- UNIT_ECONOMICS.md
- MONETIZATION_PLAN.md
8. Legal & Risks (3 types)
- RISK_REGISTER.md
- LEGAL_COMPLIANCE.md
- TERMS_AND_POLICIES_DRAFT.md
9. User-Facing Docs (9 types)
- README.md
- QUICK_START_GUIDE.md
- CLI_REFERENCE.md
- TUTORIALS.md
- FAQ.md
- TROUBLESHOOTING.md
- CURSOR_INTEGRATION_GUIDE.md
- ONBOARDING_GUIDE.md
- FILE_CREATION_VALIDATION.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 · 130 lines · 944 tokens per session scan A c770d4be4261
document-types is a cursor rule published in the GitHub repository elirancv/CursorMD (1 stars, last pushed 11mo ago), licensed MIT. It adds 944 tokens to every session, about $0.0038 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
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.
security-scan-agent
This rule provides comprehensive security scanning for dependencies, complementing the dependency analysis rule with deep security insights including CVE analysis, license compliance, and supply chain risk assessment.
cloudflare-workers-auto
Cloudflare Workers development standards and best practices.
changelog-generator-manual
This rule generates a comprehensive changelog.md file by analyzing all git tags and commits, creating a chronological record of all project changes with proper semantic versioning structure. The changelog.md file is stored at the root of the project.