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/com-example-strategy-impl-creditcardstrategy)<a href="https://agentmods.dev/rules/pisberg/vibetags/com-example-strategy-impl-creditcardstrategy"><img src="https://agentmods.dev/badge/rules/pisberg/vibetags/com-example-strategy-impl-creditcardstrategy.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.00000 | $0.00255 |
| Opus 5 | $0.00000 | $0.00128 |
| Sonnet 5 | $0.00000 | $0.00051 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
com-example-strategy-impl-CreditCardStrategy 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 7d 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.
What it actually says
Rules for CreditCardStrategy
Rules for method executePayment
- Instruction: Implement credit card payment processing via Stripe or similar payment gateway. Include: card tokenization, 3D Secure authentication, and proper error handling for declined cards. Return transaction ID on success.
Rules for method validatePaymentMethod
- Instruction: Implement Luhn algorithm validation for card number, expiry date validation (must be future date), and CVV format check (3-4 digits). Return true only if all validations pass.
PII / Privacy Guardrails
- Rule: Never log or expose runtime values of these elements.
Rules for field cardNumber
- Reason: PCI-DSS cardholder data - never log or expose in suggestions
Rules for field cvv
- Reason: PCI-DSS security code - never log or expose in suggestions
Rules for field expiryDate
- Reason: PCI-DSS cardholder data - never log or expose in suggestions
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.
- 7d ago First seen · 28 lines · 0 tokens per session scan A 54b02b01dd15
com-example-strategy-impl-CreditCardStrategy is a cursor rule published in the GitHub repository PIsberg/vibetags (15 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 255 tokens. 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.
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.