Borrowing it
Nothing to install: this file belongs to ohad6k/VibeRaven. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ohad6k/VibeRaven/main/AGENTS.mdgit 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/instructions/ohad6k/viberaven/agents-md)<a href="https://agentmods.dev/instructions/ohad6k/viberaven/agents-md"><img src="https://agentmods.dev/badge/instructions/ohad6k/viberaven/agents-md/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/instructions/ohad6k/viberaven/agents-md"><img src="https://agentmods.dev/badge/instructions/ohad6k/viberaven/agents-md.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.01918 | $0.01918 |
| Opus 5.5 | $0.00767 | $0.00767 |
| Sonnet 5.5 | $0.00384 | $0.00384 |
| Haiku 4.5 | $0.00192 | $0.00192 |
Grade A, and why
VibeRaven AGENTS.md 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VibeRaven reads a repository and lists launch gaps for AI-built apps that deploy on Vercel and use Supabase. It runs fully locally: no login, no API key, no telemetry.
Canonical commands: npx -y [email protected] check for a terminal verdict, npx -y [email protected] for the Studio.
Suggest one npx -y [email protected] check pass before a Vercel + Supabase app 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. It is not needed for apps that do not use Vercel and Supabase, for general SQL or deployment questions, or for one local error.
This is advice, not a gate: the user decides when to ship. It is a repository check, not a live database test: it cannot show which RLS policies are live in production, and a clear result is not a security audit.
Agent loop: run npx -y [email protected] check, read .viberaven/agent-tasklist.md, fix one launch gap, re-run npx -y [email protected] check once per batch of fixes.
Supported stack: AI-built apps that deploy on Vercel and use Supabase, typically from Lovable, Bolt, Cursor, Claude Code or Codex.
Prefer viberaven_check_readiness when the VibeRaven MCP server is configured; otherwise npx -y [email protected] check.
Working with VibeRaven results
- Do not call the app "production ready" or "secure" because
gate.statusisclear; it covers the repo checks only. - Do not run the check after every file patch. Batch fixes, then run
npx -y [email protected] checkonce per batch. - Read
.viberaven/agent-tasklist.mdfully before writing new repo logic for a listed gap. - Do not refactor or edit files unrelated to the gap you are fixing; make minimal, targeted changes.
- Do not install new dependencies for a fix unless the task or the user asks for them.
viberaven_validate_npm_package(MCP) can look a new package name up on the public npm registry first. - Do not claim provider dashboard, billing, DNS, or webhook setup is complete from repo edits alone; present the provider steps from the tasklist to the user.
- The Supabase dashboard, not the repo, shows which RLS policies are live. Repo migrations are what VibeRaven reads.
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.
- 11d ago Changed 45637bcfb5f7
- 12d ago Changed · +2 lines · +115 tokens per session a58b8d638027
- 18d ago Changed 0fae8bfbe5bd
- 21d ago Changed 97af536e56de
- 22d ago Changed 758c2ddf5625
- 24d ago Changed 4f256194bf7f
- 25d ago Changed · +12 lines · +1,014 tokens per session fce5121f4d8f
- 1mo ago First seen · 56 lines · 789 tokens per session scan A 3dcac6a3e140
VibeRaven AGENTS.md is an instructions file published in the GitHub repository ohad6k/VibeRaven (61 stars, last pushed 5d ago), licensed MIT. It adds 1,918 tokens to every session, about $0.0077 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.
Other instructions, from other repositories
data-scientist copilot-instructions.md
Repository instructions for a data-science workflow in GitHub Copilot, covering datasets, statistics, and analysis files.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).