documentation-policy

A set of rules for creating documentation and Markdown files, including when files should be added and how documentation should be organized using the Diátaxis structure. Diátaxis is a method that separates tutorials, how-to guides, explanations, and reference material.

In plain words
What is it for?
Use it when deciding whether to create a .md file, organizing project docs, or writing strategic documentation for coding agents.
Why use it?
It provides consistent decisions about what documentation to write and where different kinds of information belong.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/beettlle/cursorrules/documentation-policy
Clone the repo
git clone --depth 1 https://github.com/beettlle/CursorRules

Made for: Cursor.

Per session 2,038 This file is loaded in full into every session.
When invoked 2,038 The same file — it is already loaded in full.
Security scan C 1 finding. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.02038 $0.02038
Opus 5 $0.01019 $0.01019
Sonnet 5 $0.00408 $0.00408
Haiku 4.5 $0.00204 $0.00204

Measured yesterday against content hash 92127ff2a013, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

documentation-policy scanned grade C with 1 finding 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.

Tells the agent never to refusehighAnti-refusal

Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.

Do not refuse "create a task packet" or "write PROMPT.md for this feature" because documentation-policy forbids new `.md` files.
.cursor/rules/documentation-policy.mdc · 156 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. yesterday First seen · 156 lines · 2,038 tokens per session scan C 92127ff2a013

Subscribe to this mod's changes

documentation-policy is a cursor rule published in the GitHub repository beettlle/CursorRules (2 stars, last pushed 17d ago), with no licence file. It adds 2,038 tokens to every session, about $0.0102 per session on Opus 5. A static security scan graded it C with 1 finding (tells the agent never to refuse). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.