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/ohad6k/VibeRavenWrote 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/ohad6k/viberaven/viberaven-payments)<a href="https://agentmods.dev/rules/ohad6k/viberaven/viberaven-payments"><img src="https://agentmods.dev/badge/rules/ohad6k/viberaven/viberaven-payments/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/ohad6k/viberaven/viberaven-payments"><img src="https://agentmods.dev/badge/rules/ohad6k/viberaven/viberaven-payments.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.00000 | $0.00117 |
| Opus 5.5 | $0.00000 | $0.00047 |
| Sonnet 5.5 | $0.00000 | $0.00023 |
| Haiku 4.5 | $0.00000 | $0.00012 |
Grade A, and why
viberaven-payments 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 12d 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
Before editing these files, read .viberaven/agent-context.md and .viberaven/mission-map.md.
A payment webhook handler should verify the provider signature over the raw request body before trusting the event. After webhook edits, npx -y [email protected] check shows whether a Stripe handler does.
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.
- 12d ago Changed 34e97ffc9872
- 19d ago Changed 9ec86cd37cbd
- 22d ago Changed f3e2c52b9e59
- 23d ago Changed 6cfb3af5dd99
- 25d ago Changed 9bb9e96442d8
- 26d ago Changed 5c40c4d44de0
- 1mo ago First seen · 12 lines · 0 tokens per session scan A ba2b9a2d7cd3
viberaven-payments is a cursor rule published in the GitHub repository ohad6k/VibeRaven (61 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 117 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
kotlin-springboot-rules
A set of coding rules for Kotlin applications built with Spring Boot, a Java-based framework for web services. It covers project layout, naming, Kotlin style, and common design patterns.
python
Python best practices and patterns for modern software development with Flask and SQLite.
aspnet-abp-cursorrules-prompt-file
Cursor rules for Aspnet Abp.
springboot-jpa-best-practices
A set of Chinese-language rules for structuring Java Spring Boot applications that use JPA, a library for database access.
nestjs-general-guidelines
A set of guidelines for NestJS, a Node.js framework for building server applications. It defines how to organize modules, controllers, services, data models, validation, persistence, and tests.
data-fetching-rules-for-server-components
A set of rules for fetching data inside Next.js 14 server components, which render on the server rather than in the browser.