data-fetching

A set of Cursor rules for fetching data in Next.js applications, including server components, API routes, caching, revalidation, and error handling.

In plain words
What is it for?
Use it when building Next.js pages or API endpoints that load data. It covers native fetch calls, app/api route handlers, cache settings, and revalidation strategies.
Why use it?
It provides consistent guidance for getting data, choosing where requests belong, keeping results fresh, and returning appropriate errors.

Cursor rule 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 rules/muzaffar640/commitpress/data-fetching
Clone the repo
git clone --depth 1 https://github.com/muzaffar640/commitpress

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 488 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.00488
Opus 5 $0.00000 $0.00244
Sonnet 5 $0.00000 $0.00098
Haiku 4.5 $0.00000 $0.00049

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

Security

Grade A, and why

data-fetching 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.

.cursor/rules/data-fetching.mdc · 87 lines

What it actually says


description: globs: alwaysApply: true

Data Fetching Patterns

Server Component Data Fetching

  • Prefer fetching data directly in Server Components
  • Use the native fetch API which is automatically memoized in Next.js
  • Implement proper caching and revalidation strategies
// Example of data fetching in a Server Component
async function ProductPage({ params }: { params: { id: string } }) {
  const product = await fetchProduct(params.id);
  return <div>{product.name}</div>;
}

API Routes

  • API routes should be created in the app/api directory
  • Use the route.ts pattern for API handlers
  • Implement proper error handling and status codes
// Example API route in app/api/products/route.ts
export async function GET(request: Request) {
  try {
    const products = await fetchProducts();
    return Response.json(products);
  } catch (error) {
    return Response.json({ error: 'Failed to fetch products' }, { status: 500 });
  }
}

Caching and Revalidation

  • Use appropriate cache settings for fetch requests
  • Implement revalidation strategies based on data requirements:
// Example with revalidation time
async function fetchData() {
  const res = await fetch('https://api.example.com/data', { 
    next: { revalidate: 3600 } // Revalidate every hour
  });
  return res.json();
}

// Example with no caching for dynamic data
async function fetchDynamicData() {
  const res = await fetch('https://api.example.com/dynamic-data', { 
    cache: 'no-store' 
  });
  return res.json();
}

Error Handling

  • Implement robust error handling for data fetching
  • Use try/catch blocks to handle errors
  • Create appropriate error UI with error.tsx files

Parallel Data Fetching

  • Use Promise.all for parallel data fetching when appropriate:
async function ParallelFetchExample() {
  const [data1, data2] = await Promise.all([
    fetchFirstDataSource(),
    fetchSecondDataSource()
  ]);
  
  return <Component data1={data1} data2={data2} />;
}
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 · 87 lines · 0 tokens per session scan A f0b5a80ea895

Subscribe to this mod's changes

data-fetching is a cursor rule published in the GitHub repository muzaffar640/commitpress (7 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 488 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.