create-server-component

A command for creating a Next.js Server Component that loads data on the server and includes page metadata and loading handling. Server Components render without sending their component code to the browser.

In plain words
What is it for?
Creating route pages in the app directory, fetching data, generating titles and Open Graph details, handling not-found cases, and using Suspense or loading files for slow content.
Why use it?
It provides a standard structure for pages that fetch data, handle missing or failed results, show loading states, and describe themselves to search engines and social platforms.

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-component
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 440 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.00440
Opus 5 $0.00000 $0.00220
Sonnet 5 $0.00000 $0.00088
Haiku 4.5 $0.00000 $0.00044

Measured 2d ago against content hash 1615020d9ca6, 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-component 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-component.md · 74 lines

What it actually says

Create Server Component (Next.js)

Overview

Create a Next.js Server Component that fetches data on the server with proper metadata and loading states.

Steps

  1. Create page file

    • Place in app directory following route structure
    • Use async function for data fetching
  2. Add metadata

    • Use generateMetadata for dynamic metadata
    • Include title, description, OpenGraph tags
  3. Fetch data

    • Fetch directly in component (no useEffect)
    • Add proper error handling
    • Configure caching/revalidation
  4. Add Suspense boundaries

    • Wrap slow sections in Suspense
    • Create loading.tsx for route-level loading

Template

import { Suspense } from 'react';
import { notFound } from 'next/navigation';

interface PageProps {
  params: { id: string };
  searchParams: { [key: string]: string | string[] | undefined };
}

export async function generateMetadata({ params }: PageProps) {
  const data = await fetchData(params.id);
  
  return {
    title: data.title,
    description: data.description,
    openGraph: {
      title: data.title,
      images: [{ url: data.image }],
    },
  };
}

export default async function Page({ params }: PageProps) {
  const data = await fetchData(params.id);

  if (!data) notFound();

  return (
    <div className="container mx-auto p-6">
      <h1 className="text-3xl font-bold">{data.title}</h1>
      
      <Suspense fallback={<LoadingSkeleton />}>
        <AsyncContent id={params.id} />
      </Suspense>
    </div>
  );
}

export const revalidate = 3600; // ISR - 1 hour

Checklist

  • Async function used
  • Metadata generated
  • Data fetching implemented
  • Error handling (notFound, try-catch)
  • Suspense boundaries added
  • Caching strategy configured
  • TypeScript types defined
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 · 74 lines · 0 tokens per session scan A 1615020d9ca6

Subscribe to this mod's changes

create-server-component 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 440 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.