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/smeubank/cursor-templateWrote 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/smeubank/cursor-template/documentation-style-guide)<a href="https://agentmods.dev/rules/smeubank/cursor-template/documentation-style-guide"><img src="https://agentmods.dev/badge/rules/smeubank/cursor-template/documentation-style-guide/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/smeubank/cursor-template/documentation-style-guide"><img src="https://agentmods.dev/badge/rules/smeubank/cursor-template/documentation-style-guide.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.01262 |
| Opus 5.5 | $0.00000 | $0.00505 |
| Sonnet 5.5 | $0.00000 | $0.00252 |
| Haiku 4.5 | $0.00000 | $0.00126 |
Grade A, and why
documentation-style-guide 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 2mo 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Style Guide
🎯 Purpose
This guide defines writing standards for .cursor/rules/*.mdc files in the project template. These files serve as both AI assistant instructions and developer documentation.
📋 Structure Requirements
File Header Format
# [Feature/Pattern Name]
Brief description of the feature or pattern (1-2 sentences max).
## 🎯 [Section Name]
Standard Sections
- Overview - Brief purpose and scope
- When to Use - Specific scenarios with bullet points
- Implementation Pattern - Minimal code examples
- Key Conventions - Project-specific rules
- References - Links to actual implementation files
Section Ordering
- Context first (what and why)
- Implementation details (how)
- Examples and patterns
- Checklists and verification
✍️ Writing Standards
Language Guidelines
- Direct language: "Use X for Y" not "You might consider using X"
- Active voice: "Configure Sentry" not "Sentry should be configured"
- Imperative mood: "Handle errors gracefully" not "Errors should be handled gracefully"
- Present tense: "TypeScript validates" not "TypeScript will validate"
Content Guidelines
- Assume intelligence: Skip basic programming concepts
- Focus on domain-specific patterns: Not general Next.js or React patterns
- Code over prose: Show implementation patterns, minimize explanation
- Concrete examples: Use actual file paths and real code snippets
- Context window optimization: Every line provides unique value
Example Transformations
❌ BAD: "You might want to consider using TypeScript for better type safety"
✅ GOOD: "Use TypeScript with strict mode for all components"
❌ BAD: "It's generally recommended to handle errors properly"
✅ GOOD: "Log all errors to Sentry with structured context"
❌ BAD: "This is a common pattern in React applications"
✅ GOOD: "Business validation follows this pattern"
📝 Code Example Standards
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.
- 2mo ago First seen · 189 lines · 0 tokens per session scan A c715464d95b1
documentation-style-guide is a cursor rule published in the GitHub repository smeubank/cursor-template (6 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,262 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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.