Borrowing it
Nothing to install: this file belongs to benavlabs/vibe-check. 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/benavlabs/vibe-check/main/AGENTS.mdgit clone --depth 1 https://github.com/benavlabs/vibe-checkWrote 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/benavlabs/vibe-check/agents-md)<a href="https://agentmods.dev/instructions/benavlabs/vibe-check/agents-md"><img src="https://agentmods.dev/badge/instructions/benavlabs/vibe-check/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/benavlabs/vibe-check/agents-md"><img src="https://agentmods.dev/badge/instructions/benavlabs/vibe-check/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.01689 | $0.01689 |
| Opus 5.5 | $0.00676 | $0.00676 |
| Sonnet 5.5 | $0.00338 | $0.00338 |
| Haiku 4.5 | $0.00169 | $0.00169 |
Grade A, and why
vibe-check 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 1mo 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Rules
These rules apply to all code generated in this project. They are non-negotiable.
Secrets
- NEVER put API keys, database credentials, or tokens in frontend code (anything under src/, app/, pages/, components/, public/)
- NEVER put secret keys in environment variables prefixed with NEXT_PUBLIC_, VITE_, or REACT_APP_ (these are bundled into the client)
- NEVER hardcode credentials in source files. Use environment variables loaded server-side only
- The .env file MUST be in .gitignore before the first commit. Verify this before creating any .env file
- Use .env.example with placeholder values only, never real credentials
Database
- Enable Row Level Security on EVERY Supabase table before deployment. Default policy: deny all. Write explicit policies scoped to auth.uid()
- NEVER set a Supabase RLS policy to
USING (true)orFOR ALLwithout a WHERE condition - Firebase Security Rules MUST require
request.auth != nulland scope access torequest.auth.uid - NEVER use
pickle.loads,pickle.load, or any deserialization on user-supplied data. Use JSON for all network data exchange
Authentication and Authorization
- EVERY API route that returns or modifies user data MUST have authentication middleware that runs BEFORE the handler, not inside it
- Unauthenticated requests to protected endpoints MUST return 401
- EVERY route that takes a resource ID MUST verify the authenticated user owns that resource:
current_user.id == resource.owner_id. This is a SEPARATE check from authentication - Admin endpoints MUST verify admin role and return 403 for non-admin users
- Session cookies MUST set
httpOnly: true,secure: true, andsameSite: 'lax'
Input and Output
- NEVER concatenate user input into SQL queries. ALWAYS use parameterized queries or ORM methods
- NEVER use
dangerouslySetInnerHTML,v-html, orinnerHTMLwith user-supplied content unless it is first sanitized with DOMPurify - ALL user input MUST be validated server-side. Client-side validation is for UX only
- File uploads MUST validate file type by reading magic bytes, not by checking the filename extension. Rename all uploads to UUIDs server-side. Store on a separate domain (S3, R2, GCS), never on the app origin
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.
- 1mo ago Changed · +27 lines · +618 tokens per session 4292e6834b0f
- 1mo ago First seen · 85 lines · 1,071 tokens per session scan A 46d4321353bc
vibe-check AGENTS.md is an instructions file published in the GitHub repository benavlabs/vibe-check (140 stars, last pushed 1mo ago), licensed MIT. It adds 1,689 tokens to every session, about $0.0068 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
whichrules copilot-instructions.md
Instructions for z35068037/whichrules, a project described as: See exactly which instructions your AI coding agent receives - and where they conflict.
plan-forge database.instructions.md
Database patterns for .NET — Dapper/EF Core 10, parameterized queries, migration strategy.
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.