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/PIsberg/vibetagsWrote 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/pisberg/vibetags/windsurfrules)<a href="https://agentmods.dev/rules/pisberg/vibetags/windsurfrules"><img src="https://agentmods.dev/badge/rules/pisberg/vibetags/windsurfrules/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.
<a href="https://agentmods.dev/rules/pisberg/vibetags/windsurfrules"><img src="https://agentmods.dev/badge/rules/pisberg/vibetags/windsurfrules.svg" alt="Reviewed on agentmods" width="80" 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.01801 | $0.01801 |
| Opus 5 | $0.00901 | $0.00901 |
| Sonnet 5 | $0.00360 | $0.00360 |
| Haiku 4.5 | $0.00180 | $0.00180 |
Grade A, and why
windsurfrules 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.
How it starts
The opening of the file, as written. The whole thing — 89 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-XXXXcom.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 policycom.example.security.SecurityConfig.getMaxLoginAttempts()- Reason: Max login attempts set by security team to prevent brute forcecom.example.security.SecurityConfig.validateToken(java.lang.String)- Reason: Token validation must match auth server exactly. Changes will break all client authenticationcom.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.
com.example.database.DatabaseConnector- Required Checks: SQL Injection, Thread Safety issues
🚫 IGNORED ELEMENTS (EXCLUDE FROM CONTEXT)
Do not reference, suggest changes to, or include the following in completions or answers.
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.
- 2d ago First seen · 89 lines · 1,801 tokens per session scan A eeb814111877
windsurfrules is a cursor rule published in the GitHub repository PIsberg/vibetags (15 stars, last pushed yesterday), licensed MIT. It adds 1,801 tokens to every session, about $0.0090 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-09-06.
Other cursor rules, from other repositories
java-springboot-jpa-cursorrules-prompt-file
description: "Cursor rules for Java development with Springboot and JPA integration." globs: / alwaysApply: false.
gradle
Enforce modern Gradle build practices for Java and Android projects, focusing on Kotlin DSL, modularity, version catalogs, and performance optimizations.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
java-17-development-standards
Java-specific development standards following Effective Java, Google Java Style Guide, and modern Java 17 LTS best practices.
design-patterns
Design patterns (GoF) and file size conventions for sweagent TypeScript codebase.
database
Cursor rule "database" from ItamarZand88/awesome-agent-conventions, covering database best practices, prisma setup, prisma models, prisma queries and supabase setup.