api-validation

A set of rules for validating data sent to web API routes and server actions using Zod, a library for checking data shapes. It requires incoming values to be checked before the application uses them.

In plain words
What is it for?
Use it when implementing or reviewing Next.js API routes and server actions that receive data from forms, clients, or other systems.
Why use it?
It prevents invalid or unexpected request data from causing crashes, unsafe processing, or unclear API errors.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/vibestackdev/vibe-stack/api-validation
Clone the repo
git clone --depth 1 https://github.com/vibestackdev/vibe-stack

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 760 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00760
Opus 5 $0.00000 $0.00380
Sonnet 5 $0.00000 $0.00152
Haiku 4.5 $0.00000 $0.00076

Measured yesterday against content hash 1bdae786114f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

.cursor/rules/api-validation.mdc · 112 lines

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 })
}

Read the full file on GitHub · 112 lines

Changes

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.

  1. yesterday First seen · 112 lines · 0 tokens per session scan A 1bdae786114f

Subscribe to this mod's changes

api-validation is a cursor rule published in the GitHub repository vibestackdev/vibe-stack (7 stars, last pushed 2d ago), 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.