cursorrules

Project rules that require a security review before proposing or writing code for specified files and methods.

In plain words
What is it for?
Use them when editing the listed security, authentication, payment, tax, or other protected code.
Why use it?
They flag locked security and payment-related code and require the agent to acknowledge an audit before returning changes.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/pisberg/vibetags/cursorrules
Clone the repo
git clone --depth 1 https://github.com/PIsberg/vibetags

Made for: Cursor.

Per session 1,842 This file is loaded in full into every session.
When invoked 1,842 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.01842 $0.01842
Opus 5 $0.00921 $0.00921
Sonnet 5 $0.00368 $0.00368
Haiku 4.5 $0.00184 $0.00184

Measured 2d ago against content hash 9a259caa5a27, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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.

examples/basic/.cursorrules · 91 lines

How it starts

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

VIBETAGS-START

AUTO-GENERATED AI RULES

Generated by VibeTags | https://github.com/PIsberg/vibetags

Do not edit manually.

LOCKED FILES (DO NOT EDIT)

  • com.example.payment.PaymentProcessor - Reason: Tied to legacy database schema v2.3. Changes will break production payment processing. Contact the payments team before modifying.
  • com.example.security.SecurityConfig - Reason: CRITICAL: Security configuration managed by DevOps team. Any changes require security review and approval ticket SEC-XXXX
  • com.example.security.SecurityConfig.getEncryptionAlgorithm() - Reason: Encryption algorithm tied to compliance requirements (PCI-DSS)
  • com.example.security.SecurityConfig.getKeyRotationHours() - Reason: Key rotation period mandated by company policy
  • com.example.security.SecurityConfig.getMaxLoginAttempts() - Reason: Max login attempts set by security team to prevent brute force
  • com.example.security.SecurityConfig.validateToken(java.lang.String) - Reason: Token validation must match auth server exactly. Changes will break all client authentication
  • com.example.service.OrderService.calculateTax(java.lang.String,double) - Reason: Tax calculation uses Avalara API integration. Credentials and endpoint configuration managed by finance team.
  • com.example.service.OrderService.processPayment(java.lang.String,double) - Reason: Payment processing uses Stripe API v2024.10. Changes require PCI compliance review.
  • com.example.service.OrderService.validateOrder(java.util.Map<java.lang.String,java.lang.Object>) - Reason: Order validation implements 47 business rules. Last changed in Q2 2024 after 3-month testing cycle. DO NOT MODIFY without running full test suite.

🛡️ MANDATORY SECURITY AUDITS

When proposing edits or writing code for the following files, you MUST perform a security review before outputting the final code. You must explicitly state in your response that you have audited the changes for the required vulnerabilities.

  • com.example.database.DatabaseConnector
    • Required Checks: SQL Injection, Thread Safety issues

Read the full file on GitHub · 91 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. 2d ago First seen · 91 lines · 1,842 tokens per session scan A 9a259caa5a27

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository PIsberg/vibetags (14 stars, last pushed 2d ago), licensed MIT. It adds 1,842 tokens to every session, about $0.0092 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-30.