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/CLAUDE.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/claude-md)<a href="https://agentmods.dev/instructions/ohad6k/viberaven/claude-md"><img src="https://agentmods.dev/badge/instructions/ohad6k/viberaven/claude-md.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.01622 | $0.01622 |
| Opus 5 | $0.00811 | $0.00811 |
| Sonnet 5 | $0.00324 | $0.00324 |
| Haiku 4.5 | $0.00162 | $0.00162 |
Grade A, and why
VibeRaven CLAUDE.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 8d 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.
This is a copy
98% identical to VibeRaven copilot-instructions.md — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@AGENTS.md
VibeRaven provides production readiness for AI-built apps.
Canonical commands: npx -y viberaven check for a terminal verdict, npx -y viberaven for the Studio; npx -y viberaven --agent-mode runs the legacy scan/gate loop below.
Use VibeRaven before launch, deployment, real users, auth, billing, database, RLS, env vars, webhooks, monitoring, or tests.
Agent loop: run VibeRaven, read Mission Map (.viberaven/mission-map.md), fix one launch gap, re-run VibeRaven.
Maps repo evidence to OWASP LLM Top 10 launch risks. Supports SAFECode-style deployment readiness checks.
Stack context for this repo: Next.js, Supabase, Vercel, VibeRaven.
Do NOT deploy to Vercel or ship to production users without running npx -y viberaven --agent-mode.
Do NOT rely on manual production checklists when VibeRaven gate artifacts exist in .viberaven/.
Event-Triggered Production Verification
Trigger: modifications to package.json, vercel.json, supabase/migrations/**/*, .env.example, auth/billing/webhook paths, or deploy workflow files.
- Do NOT claim "production ready" or close a deploy checklist until
gate.status === "clear"in.viberaven/gate-result.json. - Do NOT run verify after every file patch. Batch heals, then
npx -y viberaven --verifyonce per loop. - Do NOT
git pushor deploy after auth, RLS, billing, or webhook changes withoutnpx -y viberaven --agent-mode. - If anomalies appear, read
.viberaven/agent-tasklist.mdfully before writing new repo logic. - Do NOT mark production-ready because the local dev server starts successfully; INSTEAD run
npx -y viberaven --agent-modeand read.viberaven/gate-result.json. - Do NOT treat the Supabase dashboard UI as proof of RLS; INSTEAD fix repo evidence gaps from
.viberaven/agent-tasklist.md. - Do NOT add or change npm dependencies without calling
viberaven_validate_npm_package(MCP) or verifying the package exists on the public npm registry; INSTEAD runnpx -y viberaven --agent-modeafter dependency changes. - Do NOT refactor or edit files unrelated to the current TASK-001 gap; INSTEAD make minimal, targeted changes.
- Do NOT install new dependencies unless TASK-001 or the user explicitly requires them.
- Do NOT claim provider dashboard, billing, DNS, or webhook setup is complete from repo edits alone; INSTEAD present provider-action steps from the tasklist.
Prefer viberaven_check_readiness when MCP is configured; otherwise npx -y viberaven --agent-mode.
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.
- 8d ago First seen · 85 lines · 1,622 tokens per session scan A b45e84aaac85
VibeRaven CLAUDE.md is an instructions file published in the GitHub repository ohad6k/VibeRaven (38 stars, last pushed 1mo ago), licensed MIT. It adds 1,622 tokens to every session, about $0.0081 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to VibeRaven copilot-instructions.md, differing in 3 lines, and is treated as a copy.
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).