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/luxvil/ai-coding-rules/80-vibe-codinggit clone --depth 1 https://github.com/Luxvil/ai-coding-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.00000 | $0.01301 |
| Opus 5 | $0.00000 | $0.00651 |
| Sonnet 5 | $0.00000 | $0.00260 |
| Haiku 4.5 | $0.00000 | $0.00130 |
Grade A, and why
80-vibe-coding 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.
This is a copy
100% identical to 80-vibe-coding — 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.
How it starts
The opening of the file, as written. The whole thing — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🎸 Vibe Coding Protocol
"The vibes are the goal. The code is the vehicle." — Vibe Coding Manifesto
When to Activate
Enable Vibe mode for:
- ✅ Prototyping and proof-of-concept
- ✅ Exploratory development
- ✅ Time-critical feature delivery
- ✅ Hackathons and MVPs
- ✅ Early-stage product validation
Do NOT use for:
- ❌ Production-critical systems
- ❌ Security-sensitive code
- ❌ Code that others will maintain immediately
- ❌ Financial or healthcare systems
Core Principles
| Traditional | Vibe Mode |
|---|---|
| Debug line by line | Reroll with better prompt |
| Get it right first time | Iterate rapidly |
| Commit when complete | Commit every working state |
| Focus on code quality | Focus on product delivery |
| Perfect is the goal | Working is the goal |
The Reroll Strategy
When to Reroll (Regenerate)
IF debugging_time > 10 minutes THEN
→ Stop debugging
→ Clarify the problem
→ Regenerate the module with better context
How to Reroll
- Identify what's not working
- Document the failure mode
- Provide clearer context/constraints
- Generate fresh implementation
- Compare and merge the best parts
This is often faster than fixing convoluted code.
Commit Checkpoint System
Rule: Every Working State = Commit
# ✅ Good commit frequency in Vibe mode
git commit -m "feat: basic form renders"
git commit -m "feat: form validates on submit"
git commit -m "feat: form submits to API"
git commit -m "fix: handle empty state"
git commit -m "feat: success toast on submit"
Why?
- Easy rollback to last working state
- Clear progress visibility
- Safe experimentation
Commit Message Format
type: short description
# Types:
feat: New feature
fix: Bug fix
wip: Work in progress (Vibe mode)
refactor: Code improvement
style: Formatting only
Speed Over Perfection
In Vibe Mode, Optimize For:
- Working software over perfect code
- User value over technical elegance
- Fast feedback over comprehensive testing
- Learning over planning
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 · 226 lines · 0 tokens per session scan A 085a294a99c3
80-vibe-coding is a cursor rule published in the GitHub repository Luxvil/ai-coding-rules (3 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,301 tokens. A static security scan graded it A with 0 findings. It is 100% identical to 80-vibe-coding, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
exam-answer-format
Guidelines for writing exam-style answers in a practical, conversational style with definitions first followed by real-world examples.
lecture-reference-linking
Guidelines for including course materials lists and inline references when writing exam answers or documentation that references course materials.
short-answer-version
Guidelines for creating short/concise versions of detailed answers.
documentation-formatting
Guidelines for formatting markdown documentation to improve readability and scannability.
mermaid-diagrams
Guidelines for adding Mermaid diagrams to exam answers and documentation with automatic SVG generation support.
human-writing-style
Rules for writing naturally and authentically - avoid robotic AI tone in documentation, code comments, error messages, and explanations. Write like a human colleague, not a customer service bot.