Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jalcantarab/v0-vibecodexnpx agentmods add rules/jalcantarab/v0-vibecodex/documentationWrote 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/jalcantarab/v0-vibecodex/documentation)<a href="https://agentmods.dev/rules/jalcantarab/v0-vibecodex/documentation"><img src="https://agentmods.dev/badge/rules/jalcantarab/v0-vibecodex/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/jalcantarab/v0-vibecodex/documentation"><img src="https://agentmods.dev/badge/rules/jalcantarab/v0-vibecodex/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.01464 | $0.01464 |
| Opus 5.5 | $0.00586 | $0.00586 |
| Sonnet 5.5 | $0.00293 | $0.00293 |
| Haiku 4.5 | $0.00146 | $0.00146 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Standards
Markdown Formatting
1. Headers and Structure
# Main Title (H1)
## Section Title (H2)
### Subsection (H3)
#### Detail Section (H4)
2. Icons and Visual Elements
Use emoji icons consistently for better navigation:
- 🚀 Getting Started: Installation and setup guides
- 📚 Documentation: Reference materials
- 🛠️ Tools: AI tools and integrations
- 🎯 Features: Project capabilities
- 🤝 Community: Contributing and support
- 📋 Checklists: Tasks and requirements
- 🔧 Configuration: Setup and settings
- 🎨 Design: UI/UX guidelines
3. Code Blocks
# Inline code
Use `backticks` for inline code references.
# Code blocks with language
```tsx
import React from 'react'
export function Component() {
return <div>Hello World</div>
}
Terminal commands
npm install
npm run dev
### 4. **Lists and Organization**
```markdown
# Unordered lists
- Item 1
- Item 2
- Sub-item 2.1
- Sub-item 2.2
# Ordered lists
1. First step
2. Second step
3. Third step
# Task lists
- [x] Completed task
- [ ] Pending task
- [ ] Future task
Documentation Structure
1. File Organization
docs/
├── README.md # Main documentation index
├── guides/ # How-to guides
│ ├── ai-development.md
│ ├── getting-started.md
│ └── contributing.md
├── reference/ # Technical reference
│ ├── api.md
│ ├── components.md
│ └── configuration.md
└── examples/ # Code examples
├── components.md
└── patterns.md
2. Page Structure
# Page Title
Brief description of what this page covers.
## 🎯 Overview
What the reader will learn from this page.
## 📋 Prerequisites
What the reader needs to know before starting.
## 🚀 Getting Started
Step-by-step instructions.
## 📚 Examples
Code examples and use cases.
## 🔗 Related Links
Links to related documentation.
Content Guidelines
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 · 265 lines · 1,464 tokens per session scan A 3f84dd3ea127
documentation is a cursor rule published in the GitHub repository jalcantarab/v0-vibecodex (8 stars, last pushed 1y ago), licensed MIT. It adds 1,464 tokens to every session, about $0.0059 per session on Opus 5.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-31.
Other cursor rules, from other repositories
clean-code
Guidelines for writing clean, maintainable, and human-readable code. Apply these rules when writing or reviewing code to ensure consistency and quality.
cursor-rules-zh
A set of rules for a Chinese-language intelligent programming assistant that chooses between a simple response and a more structured RIPER-5 workflow based on task complexity. RIPER-5 is a five-stage method for handling complex coding tasks.
cursor-rules
Intelligent programming assistant protocol - automatically selects simple direct response or complex RIPER-5 mode based on task complexity.
project-structure
Libra AI Project Structure Guidelines - Comprehensive Monorepo Architecture Rules and Best Practices.
zod-v4
Zod v4 Coding Guidelines. ALWAYS read this when using Zod.
auto-commit
Read this when user asks you to auto commit as you go.