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/vibestackdev/vibe-stackWrote 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/vibestackdev/vibe-stack/api-validation)<a href="https://agentmods.dev/rules/vibestackdev/vibe-stack/api-validation"><img src="https://agentmods.dev/badge/rules/vibestackdev/vibe-stack/api-validation/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/vibestackdev/vibe-stack/api-validation"><img src="https://agentmods.dev/badge/rules/vibestackdev/vibe-stack/api-validation.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.00760 |
| Opus 5.5 | $0.00000 | $0.00304 |
| Sonnet 5.5 | $0.00000 | $0.00152 |
| Haiku 4.5 | $0.00000 | $0.00076 |
Grade A, and why
api-validation 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.
API Route Validation Rules
RULE 1: NEVER Access Request Body Without Zod Validation
Unvalidated request bodies are the #1 source of runtime crashes and injection vulnerabilities. Every API route MUST validate the incoming body with Zod before any processing.
✅ CORRECT — validate first:
import { z } from 'zod'
import { NextRequest, NextResponse } from 'next/server'
const CreatePostSchema = z.object({
title: z.string().min(1).max(200),
content: z.string().min(1).max(10000),
published: z.boolean().default(false),
})
export async function POST(request: NextRequest) {
const body = await request.json()
const result = CreatePostSchema.safeParse(body)
if (!result.success) {
return NextResponse.json(
{ error: 'Invalid request', details: result.error.flatten() },
{ status: 400 }
)
}
const { title, content, published } = result.data
// Now safe to use
}
❌ WRONG — raw body access:
export async function POST(request: NextRequest) {
const { title, content } = await request.json() // No validation — crashes on missing fields
// title could be undefined, an object, a number — anything
}
RULE 2: Validate Server Action Parameters With Zod
Server Actions receive untyped FormData or direct calls — always validate.
✅ CORRECT:
'use server'
import { z } from 'zod'
const UpdateProfileSchema = z.object({
name: z.string().min(1).max(100),
bio: z.string().max(500).optional(),
})
export async function updateProfile(data: unknown) {
const result = UpdateProfileSchema.safeParse(data)
if (!result.success) {
return { error: result.error.flatten().fieldErrors }
}
// Process result.data safely
}
RULE 3: Always Return Consistent Error Shapes
API routes must return a consistent error shape: { error: string, details?: unknown }.
Never expose raw error messages, stack traces, or database errors to the client.
✅ CORRECT:
try {
// ... operation
} catch (error) {
console.error('[API_ERROR]', error) // Log server-side only
return NextResponse.json({ error: 'Internal server error' }, { status: 500 })
}
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 First seen · 112 lines · 0 tokens per session scan A 1bdae786114f
api-validation is a cursor rule published in the GitHub repository vibestackdev/vibe-stack (8 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 760 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-08-31.
Other cursor rules, from other repositories
payload-configuration
Shipkit conditionally initializes Payload CMS based on environment variables. The src/payload.config.ts file handles graceful degradation when no database is configured.
supabase-bootstrap
Guidelines for writing Next.js apps with Supabase Auth.
graceful-degradation
Shipkit implements graceful degradation to provide a seamless experience whether users have a database configured or not. When no DATABASEURL is provided, the application automatically falls back to local storage for data persistence.
server-actions-patterns
❌ Never export classes from "use server" files.
supabase-db-create-functions
Guidelines for writing Supabase database functions.
supabase-edge
Coding rules for Supabase Edge Functions.