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/roedyrustam/vibes-plugWrote 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/roedyrustam/vibes-plug/vibes-plug-backend)<a href="https://agentmods.dev/rules/roedyrustam/vibes-plug/vibes-plug-backend"><img src="https://agentmods.dev/badge/rules/roedyrustam/vibes-plug/vibes-plug-backend/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/roedyrustam/vibes-plug/vibes-plug-backend"><img src="https://agentmods.dev/badge/rules/roedyrustam/vibes-plug/vibes-plug-backend.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.00431 |
| Opus 5.5 | $0.00000 | $0.00172 |
| Sonnet 5.5 | $0.00000 | $0.00086 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
vibes-plug-backend 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 today.
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
Vibes-Plug Backend & Systems Engineering (2026 Edition)
When editing backend APIs, server routes, database schemas, or microservices, Cursor AI MUST enforce these standards:
1. Schema & Database Invariants
- PostgreSQL DDL: Every table MUST have
id UUID PRIMARY KEY DEFAULT gen_random_uuid(),created_at TIMESTAMPTZ NOT NULL DEFAULT now(),updated_at TIMESTAMPTZ NOT NULL DEFAULT now(). - Foreign Keys: Every foreign key MUST have an explicit index (
CREATE INDEX idx_... ON ...(...)). - Multi-Tenant Security: Every tenant-partitioned table MUST enable Row Level Security (
ALTER TABLE ... ENABLE ROW LEVEL SECURITY;) with an explicit tenant isolation policy (CREATE POLICY tenant_isolation ...). - Safe Migrations: Never use destructive
DROP TABLEorDROP COLUMNin production migrations without multi-step deprecation.
2. API Contract & Error Resilience
- Error Standard: Return RFC 9457 Problem Details (
{ type, title, status, detail, instance }) on all HTTP 4xx/5xx responses. - Validation: Strict runtime validation at every boundary using
ZodorTypeSpec. - Zero Silent Errors: Catch blocks that swallow errors (
catch (e) {}) are strictly banned. Always log structured context viaPinoorSentry. - Idempotency: All mutation endpoints (POST/PUT/PATCH) handling financial transactions or billing MUST enforce idempotency keys (
Idempotency-Keyheader with atomic database locking).
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.
- today First seen · 22 lines · 0 tokens per session scan A ef972a3d7683
vibes-plug-backend is a cursor rule published in the GitHub repository roedyrustam/vibes-plug (114 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 431 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-10-27.
Other cursor rules, from other repositories
supabase
Do not use the Supabase Client, instead use the Jawn Client and put all new endpoints in controllers. Don't use RLS policies, instead enable RLS for new tables and revoke privledges. Example.
backend-rules
A Cursor rule named backend-rules covering backend development, project structure, technology choices, runtime environment, and main process. Cursor is a coding editor with rules that guide how an agent works in a project.
crud-layer
Comprehensive guide for understanding and working with the CRUD layer in Airweave backend.
supabase-db-create-functions
Guidelines for writing Supabase database functions.
cursorrules
This document serves as some special instructions when working with Convex.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.