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/mintlify/docsWrote 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/mintlify/docs/writing-standards)<a href="https://agentmods.dev/rules/mintlify/docs/writing-standards"><img src="https://agentmods.dev/badge/rules/mintlify/docs/writing-standards/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/mintlify/docs/writing-standards"><img src="https://agentmods.dev/badge/rules/mintlify/docs/writing-standards.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.00179 | $0.00179 |
| Opus 5.5 | $0.00072 | $0.00072 |
| Sonnet 5.5 | $0.00036 | $0.00036 |
| Haiku 4.5 | $0.00018 | $0.00018 |
Grade A, and why
writing-standards 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 22d 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
Mintlify documentation writing standards
Before you write or edit content, read style-guide/README.md and the style guide files relevant to your change. The style guide is the source of truth for voice, tone, terminology, formatting, component usage, and content strategy. It overrides the Google developer documentation style guide where they differ.
For component syntax, see component-reference.mdc or the pages in components/.
Before publishing
- Preview changes locally with
mint dev. - Run
mint broken-linksto check internal links. - Run
mint a11yto check for accessibility issues. - Manually test external links to make sure they don't 404.
- Run
vale $(git diff --name-only main)to check style and spelling.
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.
- 22d ago Changed · -218 lines · -2,079 tokens per session a6e2f48bc78c
- 1mo ago First seen · 237 lines · 2,258 tokens per session scan A baaec1611f3d
writing-standards is a cursor rule published in the GitHub repository mintlify/docs (457 stars, last pushed today), licensed MIT. It adds 179 tokens to every session, about $0.0007 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-30.
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.