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/pisberg/vibetags/com-example-payment-paymentprocessorgit clone --depth 1 https://github.com/PIsberg/vibetagsWhat 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.00154 |
| Opus 5 | $0.00000 | $0.00077 |
| Sonnet 5 | $0.00000 | $0.00031 |
| Haiku 4.5 | $0.00000 | $0.00015 |
Grade A, and why
com-example-payment-PaymentProcessor 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.
What it actually says
Rules for PaymentProcessor
Locked Status
- Reason: Tied to legacy database schema v2.3. Changes will break production payment processing. Contact the payments team before modifying.
Implementation Tasks
- Instruction: Implement support for new crypto payments without breaking legacy flow.
Performance Constraints
- Rule: Optimal complexity required. O(n^2) is forbidden on hot paths.
- Constraint: HFT-level requirements: O(1) processing time expected. No database lookups in processing loop.
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 · 20 lines · 0 tokens per session scan A 100ee635639f
com-example-payment-PaymentProcessor is a cursor rule published in the GitHub repository PIsberg/vibetags (14 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 154 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
deepfake-drill
Run a tabletop drill of a voice-clone or deepfake fraud attempt — the 'CEO needs this wire today' call — against your actual approval process, before a real attacker does, then debrief the tells and fix the process gap. Use when someone asks to train the team on deepfake fraud, test wire-transfer controls, run a…
dflow-trading
DFlow trading API rules for Solana swap and prediction market integrations.
serialization-rules
Unity serialization best practices.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.