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-supabase-rls)<a href="https://agentmods.dev/rules/ohad6k/viberaven/viberaven-supabase-rls"><img src="https://agentmods.dev/badge/rules/ohad6k/viberaven/viberaven-supabase-rls/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-supabase-rls"><img src="https://agentmods.dev/badge/rules/ohad6k/viberaven/viberaven-supabase-rls.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.00089 |
| Opus 5 | $0.00000 | $0.00044 |
| Sonnet 5 | $0.00000 | $0.00018 |
| Haiku 4.5 | $0.00000 | $0.00009 |
Grade A, and why
viberaven-supabase-rls 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 10d 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 enable RLS on only one table while leaving related tables open; INSTEAD read .viberaven/mission-map.md before migration 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.
- 10d ago First seen · 10 lines · 0 tokens per session scan A 7e25eae6e3bd
viberaven-supabase-rls 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 89 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
postgresql
PostgreSQL production rules. Safe migrations, parameterized queries, TIMESTAMPTZ, proper indexing strategy.
database-access
A database access pattern that separates browser reads from server-side reads and writes when using Supabase. Supabase is a hosted PostgreSQL service with rules that can restrict which users may access rows.
user-lifecycle
Database guidance for handling a user's suspension or deletion and deciding what happens to related records through foreign-key rules.
audit-schema
Supabase audit table schema 慣例（auditlogs）.
query-optimization
A database performance rule that requires measuring PostgreSQL queries with EXPLAIN ANALYZE under the same user permissions and row-level security (RLS) conditions used in production.
db-reset-coordination
🔒 LOCKED — managed by clade Source: rules/core/db-reset-coordination.md Edit at: $CLADEHOME Local edits will be reverted by the next sync. -->.