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.
npx agentmods add rules/squirrelogic/cursor-rules/server-actionsgit clone --depth 1 https://github.com/squirrelogic/cursor-rulesWhat 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 | $0.01819 | $0.01819 |
| Opus 5 | $0.00910 | $0.00910 |
| Sonnet 5 | $0.00364 | $0.00364 |
| Haiku 4.5 | $0.00182 | $0.00182 |
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.
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 - Place all server actions in
-
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, }); }); }
-
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.
- yesterday First seen · 254 lines · 1,819 tokens per session scan A 6b80e7f46a80
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.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.