server-actions

A set of rules for Next.js server actions, functions that run on the server in response to an application request, when they read or change database data.

In plain words
What is it for?
Use it to place actions under app/actions/, store database queries and changes in lib/data/ modules, and connect them with the required server directive.
Why use it?
It keeps server actions and database operations separated, making the codebase easier to organize and maintain.

Cursor rule

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/squirrelogic/cursor-rules/server-actions
Clone the repo
git clone --depth 1 https://github.com/squirrelogic/cursor-rules
Per session 1,819 This file is loaded in full into every session.
When invoked 1,819 The same file — it is already loaded in full.
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.01819 $0.01819
Opus 5 $0.00910 $0.00910
Sonnet 5 $0.00364 $0.00364
Haiku 4.5 $0.00182 $0.00182

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

Security

Grade A, and why

server-actions 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.

nextjs/server-actions.mdc · 254 lines

How it starts

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

Server Actions with Database Operations

Overview

Best practices for implementing server actions that interact with the database through abstracted query and mutation modules.

  • File Organization

    • Place all server actions in app/actions/ directory
    • Group related actions in subdirectories by feature
    • Place database operations in separate query/mutation modules
    app/
    ├── actions/
    │   ├── auth/
    │   │   ├── login.ts
    │   │   └── register.ts
    │   └── organization/
    │       ├── create.ts
    │       └── update.ts
    lib/
    ├── data/
    │   ├── mutations/
    │   │   └── organizations.ts
    │   └── queries/
    │       └── organizations.ts
    
  • Server Action Implementation

    • Always use 'use server' directive

    • Import mutations/queries from lib/data

      // ✅ DO: Use abstracted database operations
      'use server';
      
      import { createOrganization } from '@/lib/data/mutations/organizations';
      import { getUserOrganizations } from '@/lib/data/queries/organizations';
      import { redirect } from 'next/navigation';
      
      export async function createUserOrganization(formData: FormData) {
        const name = formData.get('name') as string;
        const logoUrl = formData.get('logo_url') as string;
      
        // Get user from auth if needed
        const {
          data: { user },
        } = await supabase.auth.getUser();
      
        if (!user) {
          return redirect('/login?error=No user found');
        }
      
        const { error } = await createOrganization(name, logoUrl, user.id);
      
        if (error) {
          return redirect('/login/organization?error=Could not create organization');
        }
      
        return redirect('/welcome');
      }
      
      export async function fetchUserOrganizations() {
        const organizations = await getUserOrganizations();
        return organizations;
      }
      
      // ❌ DON'T: Mix database logic in server actions
      'use server';
      
      import { createDrizzleSupabaseClient } from '@/db';
      import { organizations } from '@/db/schema';
      
      export async function createUserOrganization(formData: FormData) {
        const db = await createDrizzleSupabaseClient();
        await db.rls(async (tx) => {
          await tx.insert(organizations).values({
            name: formData.get('name') as string,
            logo_url: formData.get('logo_url') as string,
          });
        });
      }
      

Read the full file on GitHub · 254 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 · 254 lines · 1,819 tokens per session scan A 6b80e7f46a80

Subscribe to this mod's changes

server-actions is a cursor rule published in the GitHub repository squirrelogic/cursor-rules (20 stars, last pushed 1y ago), licensed MIT. It adds 1,819 tokens to every session, about $0.0091 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.