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/zackiles/cursor-config/create-docsgit clone --depth 1 https://github.com/zackiles/cursor-configWhat 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.00000 | $0.00790 |
| Opus 5 | $0.00000 | $0.00395 |
| Sonnet 5 | $0.00000 | $0.00158 |
| Haiku 4.5 | $0.00000 | $0.00079 |
Grade A, and why
create-docs 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Local Copies of ALL External Documentation
Instructions to follow when the user has linked to a website that has documentation on it.
- SUBTASK: The user has requested you silently make local copies of all documentation linked in the current message to you. Follow the steps below before proceeding with their instructions or message.
- OBJECTIVE: Create and save comprehensive technical documents and references that are optimized for advanced agentic and document retrieval systems such as RAG.
- OUTPUT: Silently act on all steps and write the document to for the folder
.cursor/docsbefore continuing on or acting on the users message. Do NOT confirm to the users you've written the document or note that you processed documentation.
Steps for Creating Local Copies of Documentation
When this rule is manually triggered:
-
Detect External Documentation Links
- Scan the context window for URLs pointing to external documentation.
- Look for links to technical documentation sites, GitHub repositories, API references, and developer guides.
- Recognized link patterns include:
- GitHub repository documentation (README.md, docs/, wiki)
- API reference pages
- Developer guides and tutorials
- Technical documentation sites
-
Process Each Detected Link
- Fetch the full content of the linked documentation.
- For each document, follow these steps:
-
Extract and Convert Content
- Extract the full textual content of the documentation.
- Convert HTML content to clean, well-formatted Markdown.
- Preserve the document's hierarchical structure using appropriate Markdown headers.
- Maintain code blocks, lists, tables, and other structured content.
- Remove any non-textual elements (images, videos, etc.).
- Use tables to represent data models, method parameters, API inputs/outputs to maximize information density.
- Organize content logically using appropriate Markdown components:
- Headers (h1-h6) for sectioning
- Tables for structured data
- Code blocks with language specification
- Bulleted and numbered lists
- Blockquotes where appropriate
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 · 72 lines · 0 tokens per session scan A 470361e7247b
create-docs 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 790 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
css-styling
CSS architecture, tokens, and styling rules for this Docusaurus site. Apply when creating or modifying components, styles, layouts, or any UI-facing code.
docstruct
Keep project documentation clear, non-duplicated, source-of-truth driven, and token-efficient.
api
Remember: APIs are forever. Design them carefully, version them properly, and never break backward compatibility.
controllers
Remember: Controllers are just the translation layer between HTTP and your application. Keep them simple and let other layers handle complexity.
performance
Remember: Premature optimization is the root of all evil. Profile first, optimize what matters, and keep solutions maintainable.
core
Rails 8 Core Principles Guide.