create-server-action

A command for creating a Next.js Server Action that changes data on the server. It includes input validation, authentication and authorization checks, error handling, and page-data refreshes.

In plain words
What is it for?
Implementing create or update operations, validating form data with Zod, checking who is allowed to act, handling failures, and refreshing affected pages or cached data.
Why use it?
It keeps server-side changes guarded and makes updated information appear again after a form or other action changes the database.

Command 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 commands/farzannajipour/cursor-react-rules/create-server-action
Clone the repo
git clone --depth 1 https://github.com/Farzannajipour/cursor-react-rules

Made for: Cursor.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 523 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.00523
Opus 5 $0.00000 $0.00262
Sonnet 5 $0.00000 $0.00105
Haiku 4.5 $0.00000 $0.00052

Measured 2d ago against content hash c9c089d2a6c8, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

create-server-action 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 2d 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.

.cursor/commands/create-server-action.md · 88 lines

How it starts

The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create Server Action

Overview

Create a Next.js Server Action for handling mutations with validation and error handling.

Steps

  1. Create server action file

    • Place in lib/actions directory
    • Add 'use server' directive at top
  2. Add validation

    • Define Zod schema for input validation
    • Validate all inputs before processing
  3. Implement action

    • Perform database operation
    • Add authentication/authorization checks
    • Handle errors gracefully
  4. Revalidate data

    • Use revalidatePath for specific pages
    • Use revalidateTag for tagged data

Template

'use server';

import { revalidatePath } from 'next/cache';
import { z } from 'zod';
import { db } from '@/lib/db';

const schema = z.object({
  title: z.string().min(1, 'Title is required'),
  content: z.string().min(1, 'Content is required'),
});

type ActionResult = 
  | { success: true; data: any }
  | { success: false; error: string };

export async function createPost(formData: FormData): Promise<ActionResult> {
  try {
    // Validate input
    const validated = schema.parse({
      title: formData.get('title'),
      content: formData.get('content'),
    });

    // Authentication check (if needed)
    // const session = await getServerSession();
    // if (!session) {
    //   return { success: false, error: 'Unauthorized' };
    // }

    // Database operation
    const post = await db.post.create({
      data: validated,
    });

    // Revalidate affected paths
    revalidatePath('/posts');

    return { success: true, data: post };
  } catch (error) {
    console.error('Server action error:', error);
    
    if (error instanceof z.ZodError) {
      return { 
        success: false, 
        error: error.errors.map(e => e.message).join(', ') 
      };
    }
    
    return { success: false, error: 'Failed to create post' };
  }
}

Checklist

  • 'use server' directive added
  • Zod schema defined
  • Input validation implemented
  • Error handling added
  • Authentication check (if needed)
  • Database operation performed
  • revalidatePath or revalidateTag called
  • TypeScript types defined

Read the full file on GitHub · 88 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. 2d ago First seen · 88 lines · 0 tokens per session scan A c9c089d2a6c8

Subscribe to this mod's changes

create-server-action is a command published in the GitHub repository Farzannajipour/cursor-react-rules (3 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 523 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.