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.00100 |
| Opus 5 | $0.00000 | $0.00050 |
| Sonnet 5 | $0.00000 | $0.00020 |
| Haiku 4.5 | $0.00000 | $0.00010 |
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 9d 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.
Do NOT ship webhook handlers without signature verification; INSTEAD run npx -y viberaven --agent-mode after webhook edits.
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.
- 9d 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 (38 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 100 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
cloudflare-email-telegram-cursorrules-prompt-file
Cursor rules for setting up email-to-Telegram forwarding via Cloudflare Email Routing and Workers using the mail2tg CLI.
python
Python best practices and patterns for modern software development with Flask and SQLite.
react-query-cursorrules-prompt-file
Cursor rules for React development with React Query integration.
aspnet-abp-cursorrules-prompt-file
Cursor rules for Aspnet Abp.
manual-review.backend
A set of rules for verifying backend-only changes and changes that use different verification channels. It separates evidence the agent can collect from checks that require a person, a production authorization, or a business decision.
trigger
Guidelines for writing PostgreSQL triggers, which are database actions that run automatically when data changes. They explain when a trigger is appropriate and how to keep its function safe and predictable.