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/deno-kit/create-documentationgit clone --depth 1 https://github.com/zackiles/deno-kitWhat 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.00928 |
| Opus 5 | $0.00000 | $0.00464 |
| Sonnet 5 | $0.00000 | $0.00186 |
| Haiku 4.5 | $0.00000 | $0.00093 |
Grade A, and why
create-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 yesterday.
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 with-documentation — 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 — 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.
- yesterday First seen · 105 lines · 0 tokens per session scan A 50690b1aa9cb
create-documentation is a cursor rule published in the GitHub repository zackiles/deno-kit (3 stars, last pushed 5mo 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. It is 100% identical to with-documentation, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
development-conventions
Development conventions, code style, and best practices for the Kaneo project.
docs
This file provides guidelines for working with the documentation in the /docs directory.
architecture
Architecture of openapi-to-cli (ocli).
architecture-constraints
GolemBot architecture hard constraints — must check before modifying any src/ code.
app_feature_first_architecture
Feature-first architecture is a design pattern that organizes code by business features rather than technical layers. This approach promotes better maintainability, scalability, and team collaboration by keeping related functionality together and reducing coupling between different parts of the application.
best_practices
Advanced Best Practices covering Error Handling, Environment Variables, Performance, and Accessibility rules.