viberaven-core

viberaven-core is a cursor rule for Cursor from ohad6k/VibeRaven. It costs 299 tokens per session, scanned A, original, MIT.

A set of VibeRaven production rules that requires specific checks before deployment, authentication, database security, webhooks, or dependency changes.

In plain words
What is it for?
Use it to inspect the task list and project map, run checks after fixes, and perform stricter verification before continuous-integration or production releases.
Why use it?
It gives the agent a repeatable review loop and blocks promotion until the project's checks report a clear status.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/. Also seen: mentions CLAUDE.md; mentions AGENTS.md.

Good fit Use it to inspect the task list and project map, run checks after fixes, and perform stricter verification before continuous-integration or production releases.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/ohad6k/viberaven/viberaven-core
Install

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.

Clone the repo
git clone --depth 1 https://github.com/ohad6k/VibeRaven

Made for: Cursor.

Wrote 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.

agentmods badge for viberaven-core

README.md
[![agentmods](https://agentmods.dev/badge/rules/ohad6k/viberaven/viberaven-core/github.svg)](https://agentmods.dev/rules/ohad6k/viberaven/viberaven-core)
Your own site
<a href="https://agentmods.dev/rules/ohad6k/viberaven/viberaven-core"><img src="https://agentmods.dev/badge/rules/ohad6k/viberaven/viberaven-core/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.

agentmods 80×15 button for viberaven-core

Your own site · 80×15
<a href="https://agentmods.dev/rules/ohad6k/viberaven/viberaven-core"><img src="https://agentmods.dev/badge/rules/ohad6k/viberaven/viberaven-core.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 299 This file is loaded in full into every session.
When invoked 299 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00299 $0.00299
Opus 5.5 $0.00120 $0.00120
Sonnet 5.5 $0.00060 $0.00060
Haiku 4.5 $0.00030 $0.00030

Measured 13d ago against content hash eff13f9f78da, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 13d 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.

.cursor/rules/viberaven-core.mdc · 17 lines

What it actually says

For an AI-built app on Vercel and Supabase, suggest npx -y [email protected] check before it launches or is handed off, after a Supabase migration or policy change, or when the user reports a production error about RLS, env vars, the database connection, the service role key or a Stripe webhook.

This is advice, not a gate: the user decides when to ship. It is a repository check, not a live database test.

Read .viberaven/agent-tasklist.md first, then .viberaven/gate-result.json and .viberaven/mission-map.md. Fix one gap, then re-run npx -y [email protected] check once per batch. For a CI verdict: npx -y [email protected] --strict.

A clear gate.status covers the repo checks only; it is not a security audit.

Before editing these files, read .viberaven/agent-context.md and .viberaven/mission-map.md.

Full rules: AGENTS.md / CLAUDE.md (installed by npx -y [email protected] init --agents all).

Changes

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.

  1. 13d ago Changed eff13f9f78da
  2. 20d ago Changed 9c272a85616d
  3. 23d ago Changed a2b9986622f0
  4. 24d ago Changed d79b5d01ce22
  5. 26d ago Changed 1c2d30718f0e
  6. 27d ago Changed · +2 lines · +98 tokens per session 77d9833e93f4
  7. 1mo ago First seen · 15 lines · 201 tokens per session scan A bf536f214549

Subscribe to this mod's changes

viberaven-core is a cursor rule published in the GitHub repository ohad6k/VibeRaven (61 stars, last pushed 7d ago), licensed MIT. It adds 299 tokens to every session, about $0.0012 per session on Opus 5.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.