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/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/project-overview)<a href="https://agentmods.dev/rules/jalcantarab/v0-vibecodex/project-overview"><img src="https://agentmods.dev/badge/rules/jalcantarab/v0-vibecodex/project-overview.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.1 | $0.00512 | $0.00512 |
| Opus 5 | $0.00256 | $0.00256 |
| Sonnet 5 | $0.00102 | $0.00102 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
project-overview 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 8d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VibeCodex - AI Coding Starter Kit
Project Philosophy
VibeCodex is an open-source AI coding starter kit designed to help beginners create real projects with AI assistance. Our approach emphasizes:
- Approachability: Content should be welcoming and accessible to beginners
- Community-focus: Emphasize the open-source, collaborative nature
- Educational value: Highlight learning opportunities and skill development
- Practical application: Focus on building real, usable projects
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
- Deployment: Vercel
- Package Manager: pnpm
Project Structure
vibecodex/
├── app/ # Next.js App Router pages
├── components/ # Reusable React components
│ ├── ui/ # shadcn/ui components
│ └── [feature]/ # Feature-specific components
├── lib/ # Utility functions and data
├── public/ # Static assets
├── docs/ # Documentation
└── hooks/ # Custom React hooks
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
Design Language
- Colors: Violet to cyan gradients for emphasis
- Typography: Clear hierarchy with readable text
- Components: Cards with subtle shadows and rounded corners
- Icons: Lucide React with consistent sizing
- Responsive: Mobile-first design approach
AI Integration Focus
- Support for v0.dev, Bolt.new, Lovable, and Replit
- Structured prompts for consistent results
- Phase-based development approach
- Tool-specific guidance and workflows
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.
- 8d ago First seen · 59 lines · 512 tokens per session scan A d6e94644e151
project-overview is a cursor rule published in the GitHub repository jalcantarab/v0-vibecodex (8 stars, last pushed 1y ago), licensed MIT. It adds 512 tokens to every session, about $0.0026 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
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.
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.
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.