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.
npx agentmods add rules/doc2mcp/doc2mcp/ultracitegit clone --depth 1 https://github.com/doc2mcp/doc2mcpWhat 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 | $0.03481 | $0.03481 |
| Opus 5 | $0.01741 | $0.01741 |
| Sonnet 5 | $0.00696 | $0.00696 |
| Haiku 4.5 | $0.00348 | $0.00348 |
Grade A, and why
ultracite 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 2d 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.
This is a copy
100% identical to ultracite — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Context
Ultracite enforces strict type safety, accessibility standards, and consistent code quality for JavaScript/TypeScript projects using Biome's lightning-fast formatter and linter.
Key Principles
- Zero configuration required
- Subsecond performance
- Maximum type safety
- AI-friendly code generation
Before Writing Code
- Analyze existing patterns in the codebase
- Consider edge cases and error scenarios
- Follow the rules below strictly
- Validate accessibility requirements
Rules
Accessibility (a11y)
- Don't use
accessKeyattribute on any HTML element. - Don't set
aria-hidden="true"on focusable elements. - Don't add ARIA roles, states, and properties to elements that don't support them.
- Don't use distracting elements like
<marquee>or<blink>. - Only use the
scopeprop on<th>elements. - Don't assign non-interactive ARIA roles to interactive HTML elements.
- Make sure label elements have text content and are associated with an input.
- Don't assign interactive ARIA roles to non-interactive HTML elements.
- Don't assign
tabIndexto non-interactive HTML elements. - Don't use positive integers for
tabIndexproperty. - Don't include "image", "picture", or "photo" in img alt prop.
- Don't use explicit role property that's the same as the implicit/default role.
- Make static elements with click handlers use a valid role attribute.
- Always include a
titleelement for SVG elements. - Give all elements requiring alt text meaningful information for screen readers.
- Make sure anchors have content that's accessible to screen readers.
- Assign
tabIndexto non-interactive HTML elements witharia-activedescendant. - Include all required ARIA attributes for elements with ARIA roles.
- Make sure ARIA properties are valid for the element's supported roles.
- Always include a
typeattribute for button elements. - Make elements with interactive roles and handlers focusable.
- Give heading elements content that's accessible to screen readers (not hidden with
aria-hidden). - Always include a
langattribute on the html element. - Always include a
titleattribute for iframe elements. - Accompany
onClickwith at least one of:onKeyUp,onKeyDown, oronKeyPress. - Accompany
onMouseOver/onMouseOutwithonFocus/onBlur. - Include caption tracks for audio and video elements.
- Use semantic elements instead of role attributes in JSX.
- Make sure all anchors are valid and navigable.
- Ensure all ARIA properties (
aria-*) are valid. - Use valid, non-abstract ARIA roles for elements with ARIA roles.
- Use valid ARIA state and property values.
- Use valid values for the
autocompleteattribute on input elements. - Use correct ISO language/country codes for the
langattribute.
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.
- 2d ago First seen · 333 lines · 3,481 tokens per session scan A f3bdeca1f69a
ultracite is a cursor rule published in the GitHub repository doc2mcp/doc2mcp (5 stars, last pushed 1mo ago), licensed MIT. It adds 3,481 tokens to every session, about $0.0174 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to ultracite, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
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.
cli-error-handling
CLI command error handling patterns.
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.