vibe-project: Cursor rule for Cursor

.cursorrules

cursorrules is a cursor rule for Cursor from jhl-labs/vibe-project. It costs 495 tokens per session, scanned A, original, MIT.

A Cursor AI rules file that explains project coding conventions, but the older .cursorrules format is deprecated in favor of .cursor/rules/*.mdc files.

In plain words
What is it for?
Use it when maintaining a Cursor project or moving its rules into the newer MDC rule files.
Why use it?
It warns developers about the migration and gives agents guidance on structure, code quality, error handling, and tests.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/. Also seen: mentions CLAUDE.md.

This is jhl-labs/vibe-project's own configuration. It tells Cursor how to work on vibe-project itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything vibe-project configures →

Reuse

Borrowing it

Nothing to install: this file belongs to jhl-labs/vibe-project. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/jhl-labs/vibe-project/main/.cursorrules
Clone the repo
git clone --depth 1 https://github.com/jhl-labs/vibe-project

Made for: Cursor.

Wrote 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.

agentmods badge for cursorrules

README.md
[![agentmods](https://agentmods.dev/badge/rules/jhl-labs/vibe-project/cursorrules/github.svg)](https://agentmods.dev/rules/jhl-labs/vibe-project/cursorrules)
Your own site
<a href="https://agentmods.dev/rules/jhl-labs/vibe-project/cursorrules"><img src="https://agentmods.dev/badge/rules/jhl-labs/vibe-project/cursorrules/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.

agentmods 80×15 button for cursorrules

Your own site · 80×15
<a href="https://agentmods.dev/rules/jhl-labs/vibe-project/cursorrules"><img src="https://agentmods.dev/badge/rules/jhl-labs/vibe-project/cursorrules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 495 This file is loaded in full into every session.
When invoked 495 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00495 $0.00495
Opus 5.5 $0.00198 $0.00198
Sonnet 5.5 $0.00099 $0.00099
Haiku 4.5 $0.00049 $0.00049

Measured 2mo ago against content hash cf4a5e5102db, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.cursorrules · 78 lines

How it starts

The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cursor AI Rules

⚠️ DEPRECATION NOTICE

─────────────────────────────────────────────────────────────

This .cursorrules file format is DEPRECATED.

Cursor will remove support for this format in a future release.

Please migrate to the new Project Rules system:

📁 .cursor/rules/*.mdc

This template includes both formats for compatibility:

- .cursor/rules/general.mdc (always applied)

- .cursor/rules/typescript.mdc (*.ts, *.tsx, *.js, *.jsx)

- .cursor/rules/python.mdc (*.py)

- .cursor/rules/architecture.mdc (domain, application, etc.)

Migration guide: https://docs.cursor.com/context/rules-for-ai

─────────────────────────────────────────────────────────────

You are an expert developer working on this project. Follow these rules strictly.

Project Context

  • Project:
  • Language:

Core Rules

  1. Follow existing code patterns and conventions
  2. Write clean, maintainable, well-documented code
  3. Keep functions small and focused (max 30 lines)
  4. Include proper error handling
  5. Write tests for new functionality

Architecture

Follow layered/clean architecture:

  • Domain: Pure business logic (no external dependencies)
  • Application: Use cases and orchestration
  • Infrastructure: External services, DB
  • Presentation: API/UI layer

Dependencies flow inward (Dependency Inversion).

Security (CRITICAL)

NEVER:

  • Hardcode secrets or credentials
  • Use eval() or dynamic code execution
  • Trust user input without validation
  • Expose sensitive data in logs

ALWAYS:

  • Validate and sanitize all inputs
  • Use parameterized queries
  • Use environment variables for configuration

Git

  • Conventional commits: type(scope): description
  • Atomic commits with clear messages

Response Format

When generating code:

  1. Explain approach briefly
  2. Provide complete implementation
  3. Include necessary imports
  4. Add comments for complex logic

Context Files

For detailed rules, see:

  • .cursor/rules/*.mdc - Project Rules (NEW, recommended)
  • CLAUDE.md - Full project instructions
  • .agent/context.md - Project context
  • .agent/conventions.md - Coding conventions

Read the full file on GitHub · 78 lines

Changes

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.

  1. 2mo ago First seen · 78 lines · 495 tokens per session scan A cf4a5e5102db

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository jhl-labs/vibe-project (2 stars, last pushed 9mo ago), licensed MIT. It adds 495 tokens to every session, about $0.0020 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.

Related

cursorrules compared with cursor rules from other repositories

cursorrules next to 6 cursor rules from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
cursorrulesjhl-labs/vibe-projectCursor rule29mo agoMITA495Cursor
testing-bdd-for-appsSyntaxArc/archipy-pluginCursor rule35d agoMITA2,299Cursor
using-archipy-modelsSyntaxArc/archipy-pluginCursor rule35d agoMITA2,041Cursor
using-archipy-adaptersSyntaxArc/archipy-pluginCursor rule35d agoMITA1,181Cursor
using-archipy-servicesSyntaxArc/archipy-pluginCursor rule35d agoMITA1,551Cursor
using-archipy-utilsSyntaxArc/archipy-pluginCursor rule35d agoMITA1,363Cursor
config-and-diSyntaxArc/archipy-pluginCursor rule35d agoMITA981Cursor