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/mitas/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/mitas/cursor-rules/formatting)<a href="https://agentmods.dev/rules/mitas/cursor-rules/formatting"><img src="https://agentmods.dev/badge/rules/mitas/cursor-rules/formatting/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/mitas/cursor-rules/formatting"><img src="https://agentmods.dev/badge/rules/mitas/cursor-rules/formatting.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.01163 |
| Opus 5.5 | $0.00000 | $0.00465 |
| Sonnet 5.5 | $0.00000 | $0.00233 |
| Haiku 4.5 | $0.00000 | $0.00116 |
Grade A, and why
formatting 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Markdown Formatting Standards
Context
- Ensures consistent formatting and structure in Markdown documents.
- Helps maintain readability and professional appearance.
- Applies to all Markdown document creation and editing.
- Enables better documentation and knowledge sharing.
- Creates consistent experience across different Markdown renderers.
- A well-formatted document is the first impression of your repository.
- Good documentation encourages adoption and collaboration.
- Following best practices improves discoverability and usability.
- Visual elements enhance engagement and comprehension.
Critical rules
- Follow Markdown best practices for formatting.
- Maintain clear document structure with proper heading hierarchy.
- Use Mermaid UML diagrams for documenting complex sequences or architecture.
- Maximum heading depth: 4 levels (h1-h4).
- Indent content within XML tags by 2 spaces.
- Code blocks must indicate the language properly after the initial 3 backticks.
- Keep tables properly aligned with consistent spacing.
- Use blank lines between different content blocks for readability.
- Use proper list formatting: unordered lists with
-and ordered lists with numbers. - Use descriptive link text rather than raw URLs.
- Include alt text for images.
- Keep line length under 120 characters for better readability.
- Use fenced code blocks with language specifiers instead of indented code blocks.
- End all sentences with a period to maintain proper grammar and readability.
- Use proper heading capitalization (title case for h1-h2, sentence case for h3-h4).
- Add a space after list markers (- or numbers) for consistent rendering.
- Use consistent emphasis formatting (either * or _ for italics/bold, not mixed).
- Use concise, scannable paragraphs with 3-5 sentences maximum.
- Incorporate visual elements strategically:
- Screenshots of the application in use
- Diagrams explaining architecture or workflows
- Logo at the top when available
- Add relevant badges at the top (build status, version, license, etc.) for README files.
- Provide working examples that demonstrate real-world usage.
- Maintain a friendly, encouraging tone throughout.
- Close with clear next steps or call-to-action.
- Keep the entire document scannable within 2-3 minutes.
- Include requirements and dependencies section in README files.
- Add a troubleshooting or FAQ section for common issues when applicable.
- Provide links to additional documentation when available.
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 · 187 lines · 0 tokens per session scan A a7827722f09f
formatting is a cursor rule published in the GitHub repository mitas/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,163 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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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).