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 commands/farzannajipour/cursor-react-rules/create-server-componentgit clone --depth 1 https://github.com/Farzannajipour/cursor-react-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.00000 | $0.00440 |
| Opus 5 | $0.00000 | $0.00220 |
| Sonnet 5 | $0.00000 | $0.00088 |
| Haiku 4.5 | $0.00000 | $0.00044 |
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.
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
-
Create page file
- Place in app directory following route structure
- Use async function for data fetching
-
Add metadata
- Use generateMetadata for dynamic metadata
- Include title, description, OpenGraph tags
-
Fetch data
- Fetch directly in component (no useEffect)
- Add proper error handling
- Configure caching/revalidation
-
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
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.
- 2d ago First seen · 74 lines · 0 tokens per session scan A 1615020d9ca6
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.
Other commands, from other repositories
auto-browse
Auto-browse — learn, optimize, and graduate browser operations or web data-mining workflows.
research-perplexity
Run a deep research query using Perplexity's /research mode via Playwright browser automation. This is an alternative to /export-to-council that uses Perplexity's dedicated research mode instead of multi-model council.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
review
Compare a reference design against an implementation. Accepts Figma URL, image file, or browser URL as reference.
graphify
Turn your vault into a clustered knowledge graph with HTML and JSON outputs.
laravel-playwright
E2E Playwright patterns; use the laravel:e2e-playwright skill exactly as written.