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/zackiles/cursor-configWrote 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/zackiles/cursor-config/with-documentation)<a href="https://agentmods.dev/rules/zackiles/cursor-config/with-documentation"><img src="https://agentmods.dev/badge/rules/zackiles/cursor-config/with-documentation/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/zackiles/cursor-config/with-documentation"><img src="https://agentmods.dev/badge/rules/zackiles/cursor-config/with-documentation.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.00928 |
| Opus 5.5 | $0.00000 | $0.00371 |
| Sonnet 5.5 | $0.00000 | $0.00186 |
| Haiku 4.5 | $0.00000 | $0.00093 |
Grade A, and why
with-documentation 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- create-documentation — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
How to Write Documentation
DANGER: You must follow the rules in Style and Prose, and Format and Output when doing the following:
- Writing or editing documentation
- Responding technically or on a technical topic to the user
- Reviewing or proposing changes to documentation
Style and Prose
- Sentences using the dependency grammar framework instead of phrase structure grammar
- Sentences should be brief and action-oriented
- Sentence-style capitalization and serial commas consistently
- Subject-verb-object order for clarity and rhythm
- Clear and active constructions
- Verbs instead of nominalized nouns
- Specific nouns and clear referents to eliminate ambiguity
- Plain language or clearly explains necessary jargon
- Consistent grammatical structure across headings, instructions, and examples
- Parallel structure in lists to improve scanability and comprehension
- Words connected in close proximity to each other improve comprehension
- Concise language, active voice, and consistent structure
- Second person ("you") to address readers
- Imperative verbs for clear instructions
- Place conditions before actions
- Numbered lists for sequential steps
- Bullet lists for non-sequential items
- Instructions are task-oriented and start with verbs, such as "Click," "Select," or "Enter."
- Descriptive and informative link text rather than generic terms like "click here" or "more information."
- Consistent and precise terminology
- Prefer familiar terms over ambiguous or novel ones
- Define new or complex terms when first used
- Introduce abbreviations and acronyms before using them
- Use abbreviations consistently and sparingly
- Keep spelling, capitalization, and hyphenation uniform
- Format code and commands in
monospace - Keep code lines under 80 characters
- Show user input, system output, and examples clearly
- Use sentence case for headings
- Use clear subheadings and indent lists properly
- Break steps into short, clear actions
- Use tested, realistic technical examples
- Most important information at the beginning of each sentence
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 · 105 lines · 0 tokens per session scan A 50690b1aa9cb
with-documentation is a cursor rule published in the GitHub repository zackiles/cursor-config (17 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 928 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-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.