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/steipete/agent-rules/create-docsgit clone --depth 1 https://github.com/steipete/agent-rulesWhat 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.00284 | $0.00284 |
| Opus 5 | $0.00142 | $0.00142 |
| Sonnet 5 | $0.00057 | $0.00057 |
| Haiku 4.5 | $0.00028 | $0.00028 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- create-docs — 100% identical, 0 lines differ
What it actually says
Create Docs
Create comprehensive documentation for specified components or features.
Analysis Areas:
- Code structure and purpose
- Inputs, outputs, and behavior
- User interaction flows
- Edge cases and error handling
- Integration points with other components/systems
Documentation Template:
Overview
Brief 1-2 paragraph overview explaining purpose and value
Usage
How to use this component/feature with examples
API / Props / Parameters
Detailed specification of interfaces
Component Hierarchy
Structure and relationships (if applicable)
State Management
How state is handled and flows through the system
Behavior
Expected behavior in different scenarios
Error Handling
How errors are caught, handled, and reported
Performance Considerations
Optimization notes and performance characteristics
Accessibility
Accessibility features and compliance
Testing
How to test this component/feature
Related Components/Features
Links to related documentation
Process:
- Analyze the target code thoroughly
- Identify all public interfaces
- Document expected behaviors
- Include code examples
- Add diagrams where helpful
- Follow project documentation standards
- Ensure clarity, completeness, and actionability
Output Formats:
- Markdown for general documentation
- JSDoc/TSDoc for code comments
- API documentation format
- README files
- Architecture decision records (ADRs)
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 · 61 lines · 284 tokens per session scan A cd543301b4f3
create-docs is a cursor rule published in the GitHub repository steipete/agent-rules (5,696 stars, last pushed 4mo ago), licensed MIT. It adds 284 tokens to every session, about $0.0014 per session on Opus 5. 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
code-optimization
Guidelines for optimizing duplicate and poorly structured code.
paperfit
PaperFit project rule for LaTeX visual typesetting optimization.
read-xlsx
Reading, writing, diffing, and repairing spreadsheets (.xlsx) for AI agents via the xfa MCP server.
coding-standards-demo.crux
Team coding standards and best practices.
testing
Always use vitest for testing. Use describe/it blocks.
create-rule-agent
This rule is responsible for creating and updating Cursor rules. Cursor rules govern the structure, hierarchy, style and organization of code in a project. This rule should be invoked in Agent mode when: 1. a user wants to create a new cursor rule, 2. a user wants to update or change an existing rule, 3. user wants…