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/roy2392/vibe-agents-rulesWrote 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/roy2392/vibe-agents-rules/create-docs)<a href="https://agentmods.dev/rules/roy2392/vibe-agents-rules/create-docs"><img src="https://agentmods.dev/badge/rules/roy2392/vibe-agents-rules/create-docs/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/roy2392/vibe-agents-rules/create-docs"><img src="https://agentmods.dev/badge/rules/roy2392/vibe-agents-rules/create-docs.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.00284 | $0.00284 |
| Opus 5.5 | $0.00114 | $0.00114 |
| Sonnet 5.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 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.
This is a copy
100% identical to create-docs — 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.
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.
- 1mo ago First seen · 61 lines · 284 tokens per session scan A cd543301b4f3
create-docs is a cursor rule published in the GitHub repository roy2392/vibe-agents-rules (10 stars, last pushed 1y ago), licensed MIT. It adds 284 tokens to every session, about $0.0011 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to create-docs, differing in 0 lines, and is treated as a copy.
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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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).