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/cmnemoi/cursor-rulesWrote 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/cmnemoi/cursor-rules/006-project-documentation)<a href="https://agentmods.dev/rules/cmnemoi/cursor-rules/006-project-documentation"><img src="https://agentmods.dev/badge/rules/cmnemoi/cursor-rules/006-project-documentation/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/cmnemoi/cursor-rules/006-project-documentation"><img src="https://agentmods.dev/badge/rules/cmnemoi/cursor-rules/006-project-documentation.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.00000 | $0.00421 |
| Opus 5.5 | $0.00000 | $0.00168 |
| Sonnet 5.5 | $0.00000 | $0.00084 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
006-project-documentation 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.
What it actually says
Project Documentation Standards
1.0.0
Context
- These rules apply to all project documentation
- They ensure documentation is clear, complete, and maintainable
- They promote consistency across all documentation
- They help new team members onboard efficiently
Requirements
Documentation Structure
- Organize documentation by domain/feature
- Use a consistent structure across similar documents
- Include a table of contents for documents longer than 500 lines
- Maintain a clear hierarchy with proper heading levels
- Document the "why" more than the "how"
README Files
- Each project/module must have a README.md
- Include purpose, installation, and usage instructions
- Document environment requirements
- Provide quick start examples
- Link to more detailed documentation
API Documentation
- Document all public APIs using
OpenAPI - Include parameters, return values, and error responses
- Provide usage examples
- Document authentication requirements
- Keep API documentation in sync with implementation
Architecture Documentation
- Document system architecture with diagrams
- Explain key design decisions and trade-offs
- Document integration points with external systems
- Keep architecture documentation up-to-date with implementation
User Documentation
- Write in clear, non-technical language
- Include step-by-step instructions
- Provide screenshots for UI-related instructions
- Organize by user tasks rather than system features
- Include troubleshooting sections for common issues
Language and Style
- Write in English
- Use present tense
- Use active voice
- Be concise and specific
- Define technical terms and acronyms on first use
Critical Rules
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 · 68 lines · 421 tokens per session scan A 3e7ac72f6698
006-project-documentation is a cursor rule published in the GitHub repository cmnemoi/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 421 tokens. 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.