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.
npx agentmods add instructions/benavlabs/vibe-check/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.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 | $0.01071 | $0.01071 |
| Opus 5 | $0.00535 | $0.00535 |
| Sonnet 5 | $0.00214 | $0.00214 |
| Haiku 4.5 | $0.00107 | $0.00107 |
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 5d 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 — 85 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.
- 5d 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 (101 stars, last pushed 1mo ago), licensed MIT. It adds 1,071 tokens to every session, about $0.0054 per session on Opus 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
drift copilot-instructions.md
Instructions for mick-gsk/drift, covering drift — verbindliche arbeitsgrundlage für alle agenten, primärmodus bei prompt-engineering, zuerst das richtige primitive wählen, nicht verhandelbare schärferegeln and mindestvertrag für jeden guten prompt.
drift drift-push-gates.instructions.md
Nutze diese Instruction, wenn ein Commit, ein Push oder eine Release-Vorbereitung im Drift-Repo ansteht. Sie ist die autoritative Gate-Quelle fuer Pre-Push-Anforderungen, Bypaesse und lokale CI-Pflichten.
drift drift-quality-workflow.instructions.md
Nutze diese Instruction bei nicht-trivialen Aenderungen, Reviews oder Fix-Loops im Drift-Repo. Fokus: adversarialer Gegenreview, iterativer Fix-Loop, expliziter Freigabestatus und Human-in-the-Loop vor Merge.
drift drift-agent-quickref.instructions.md
Kompakte Task-zu-Gate Kurzanleitung fuer Drift-Agenten. Verwenden fuer schnellen Einstieg bei feat, fix, signal, chore, prompt und review Aufgaben.
drift drift-rag-grounding.instructions.md
Nutze diese Instruction, wenn ein Coding-Agent Behauptungen ueber drifts eigene Policy, Signale, ADR-Entscheidungen, Audit-Ergebnisse oder Benchmark-Evidence aufstellt. Sie verpflichtet zur Zitation verifizierter Fact-IDs via driftretrieve und driftcite (ADR-091).
drift drift-policy.instructions.md
Nutze diese Instruction immer als verbindlichen Gate-Wrapper fuer Drift-Arbeit. Sie enthaelt das Pflicht-Gate, das Kompaktformat fuer Trivialaufgaben und die Verweise auf die autoritative POLICY.md.