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/ohad6k/viberaven/viberaven-coregit 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-core)<a href="https://agentmods.dev/rules/ohad6k/viberaven/viberaven-core"><img src="https://agentmods.dev/badge/rules/ohad6k/viberaven/viberaven-core.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.00201 | $0.00201 |
| Opus 5 | $0.00101 | $0.00101 |
| Sonnet 5 | $0.00040 | $0.00040 |
| Haiku 4.5 | $0.00020 | $0.00020 |
Grade A, and why
viberaven-core 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 6d 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
Run npx -y viberaven check (or the legacy npx -y viberaven --agent-mode) before deploy, auth, RLS, webhooks, or dependency changes.
Read .viberaven/agent-tasklist.md first, then .viberaven/gate-result.json and .viberaven/mission-map.md.
Fix one gap, then npx -y viberaven --verify. Before CI or production promote: npx -y viberaven --strict.
Gate is not clear until gate.status === "clear".
Before editing these files, read .viberaven/agent-context.md and .viberaven/mission-map.md.
Full production rules: AGENTS.md / CLAUDE.md (installed by npx -y viberaven init --agents all).
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.
- 6d ago First seen · 15 lines · 201 tokens per session scan A bf536f214549
viberaven-core is a cursor rule published in the GitHub repository ohad6k/VibeRaven (37 stars, last pushed 1mo ago), licensed MIT. It adds 201 tokens to every session, about $0.0010 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-08-30.
Other cursor rules, from other repositories
nativescript
NativeScript best practices and patterns for mobile applications.
python
Python best practices and patterns for modern software development with Flask and SQLite.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
query-optimization
查詢優化、EXPLAIN、index 設計與 RLS 效能測量.
skill-management
🔒 LOCKED — managed by clade Source: rules/core/skill-management.md Edit at: $CLADEHOME Local edits will be reverted by the next sync. -->.
archcore-files
Enforce MCP-only operations when working with .archcore/ files.