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/jalcantarab/v0-vibecodex/cursorrulesgit clone --depth 1 https://github.com/jalcantarab/v0-vibecodexWrote 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/cursorrules)<a href="https://agentmods.dev/rules/jalcantarab/v0-vibecodex/cursorrules"><img src="https://agentmods.dev/badge/rules/jalcantarab/v0-vibecodex/cursorrules.svg" alt="Measured on agentmods" 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 | $0.01431 | $0.01431 |
| Opus 5 | $0.00715 | $0.00715 |
| Sonnet 5 | $0.00286 | $0.00286 |
| Haiku 4.5 | $0.00143 | $0.00143 |
Grade A, and why
cursorrules 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 5d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
⚠️ Legacy Notice (2025): This file is deprecated
As of July 2025, Cursor uses the .cursor/rules/ directory with modular .mdc files for all new projects. This .cursorrules file is supported for legacy compatibility only. Please migrate your rules to the new modular format for better organization, overrides, and AI context. See the Cursor Rules & Prompt Templates Guide for details and migration steps.
VibeCodex - AI Coding Starter Kit Rules
Project Overview
VibeCodex is an open-source AI coding starter kit designed to help beginners create real projects with AI assistance. The project emphasizes approachability, community-focus, educational value, and practical application.
Tech Stack
- Framework: Next.js 14+ with App Router
- Language: TypeScript
- Styling: Tailwind CSS
- UI Components: shadcn/ui + Radix UI
- Icons: Lucide React
- Animations: Framer Motion
- Package Manager: pnpm
Key Principles
- Beginner-Friendly: All code should be accessible to newcomers
- AI-First: Optimize for AI-assisted development workflows
- Community-Driven: Encourage contributions and collaboration
- Production-Ready: Focus on real-world applications
- Educational: Provide clear explanations and learning paths
React Component Guidelines
Component Structure
Always use functional components with hooks:
import { ComponentProps } from 'react'
import { cn } from '@/lib/utils'
interface ComponentNameProps extends ComponentProps<'div'> {
// Add specific props here
}
export function ComponentName({ className, ...props }: ComponentNameProps) {
return (
<div className={cn("base-classes", className)} {...props}>
{/* Component content */}
</div>
)
}
Key Patterns
- Use PascalCase for component names
- Export as named exports, not default exports
- Extend HTML element props when appropriate
- Use
cn()utility for className merging - Use Tailwind CSS classes consistently
- Leverage shadcn/ui components as base
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.
- 5d ago First seen · 198 lines · 1,431 tokens per session scan A 28e7c2ec4d58
cursorrules is a cursor rule published in the GitHub repository jalcantarab/v0-vibecodex (8 stars, last pushed 1y ago), licensed MIT. It adds 1,431 tokens to every session, about $0.0072 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-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
智能编程助手协议 - 根据任务复杂度自动选择简单直接回复或复杂RIPER-5模式.
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.