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/lacymorrow/paperclip-hubWrote 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/lacymorrow/paperclip-hub/server-actions-patterns)<a href="https://agentmods.dev/rules/lacymorrow/paperclip-hub/server-actions-patterns"><img src="https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/server-actions-patterns/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/lacymorrow/paperclip-hub/server-actions-patterns"><img src="https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/server-actions-patterns.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.01138 |
| Opus 5.5 | $0.00000 | $0.00455 |
| Sonnet 5.5 | $0.00000 | $0.00228 |
| Haiku 4.5 | $0.00000 | $0.00114 |
Grade A, and why
server-actions-patterns 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Server Actions & Services Patterns
Next.js "use server" Restrictions
Critical Rule: Only Async Functions in "use server" Files
❌ Never export classes from "use server" files
// This will cause build errors
"use server";
export class MyService { // ❌ BREAKS
static async method() {}
}
✅ Always use individual exported async functions
// This works correctly
"use server";
export async function myServiceMethod() { // ✅ WORKS
// implementation
}
Service Layer Pattern
Function Naming Convention
Use descriptive function names that indicate the entity and action:
// Waitlist service functions
addWaitlistEntry()
getWaitlistEntry()
updateWaitlistEntry()
deleteWaitlistEntry()
// User service functions
addUserAccount()
getUserProfile()
updateUserSettings()
Database Null Checks
Always validate database connection in service functions:
export async function serviceFunction() {
if (!db) {
throw new Error("Database not initialized");
}
// proceed with database operations
}
Server Actions Pattern
Form Handling Actions
Server actions should handle the complete user flow:
export async function handleFormSubmission(formData: FormData) {
try {
// 1. Validate input
// 2. Check business rules (duplicates, etc.)
// 3. Call service functions
// 4. Handle side effects (emails, etc.)
// 5. Return success/error response
return { success: true };
} catch (error) {
return { success: false, error: error.message };
}
}
Error Handling Pattern
Always provide user-friendly error responses:
} catch (error: unknown) {
if (error instanceof Error) {
console.error("Specific error:", error.message);
return { success: false, error: error.message };
}
console.error("Unknown error:", error);
return { success: false, error: "An unknown error occurred" };
}
Import/Export Patterns
Service Function Imports
Import specific functions, optionally with aliases:
import {
addWaitlistEntry,
isEmailOnWaitlist,
getWaitlistStats as getStats
} from "@/server/services/waitlist-service";
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 · 214 lines · 0 tokens per session scan A ab7f810d43d2
server-actions-patterns is a cursor rule published in the GitHub repository lacymorrow/paperclip-hub (15 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,138 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-11-10.
server-actions-patterns compared with cursor rules from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| server-actions-patternslacymorrow/paperclip-hub | Cursor rule | 15 | yesterday | MIT | A | 0 | Cursor |
| backendfirst-fluke/fullstack-starter | Cursor rule | 226 | 2d ago | MIT | A | 15 | Cursor |
| api-validationvibestackdev/vibe-stack | Cursor rule | 8 | yesterday | MIT | A | 0 | Cursor |
| api-designvibestackdev/vibe-stack | Cursor rule | 8 | yesterday | MIT | A | 0 | Cursor |
| server-actionskrivoox/agent-stack-template | Cursor rule | 30 | 1mo ago | MIT | A | 0 | Cursor |
| always-push-pritsmemeworks/adhx | Cursor rule | 19 | 5d ago | MIT | A | 279 | Cursor |
| workflowWebDevPeterGriffin/The-VibeCode-Bible | Cursor rule | 42 | 7d ago | none | A | 0 | Cursor |