data-fetching-rules-for-server-components

data-fetching-rules-for-server-components is a cursor rule for Cursor from claire-gong-18/awesome-cursorrules. It costs 123 tokens per session, scanned A, a copy of data-fetching-rules-for-server-components, CC0-1.0.

A set of rules for loading data inside Next.js server components, which are components rendered on the server before the page reaches the browser.

In plain words
What is it for?
Use it when writing Next.js 14 pages that fetch data from APIs and need caching or periodic data refreshes.
Why use it?
It provides a consistent way to handle failed requests and control how long fetched data is reused.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit Use it when writing Next.js 14 pages that fetch data from APIs and need caching or periodic data refreshes.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/claire-gong-18/awesome-cursorrules/data-fetching-rules-for-server-components
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.

Clone the repo
git clone --depth 1 https://github.com/claire-gong-18/awesome-cursorrules

Made for: Cursor.

Wrote 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.

agentmods badge for data-fetching-rules-for-server-components

README.md
[![agentmods](https://agentmods.dev/badge/rules/claire-gong-18/awesome-cursorrules/data-fetching-rules-for-server-components/github.svg)](https://agentmods.dev/rules/claire-gong-18/awesome-cursorrules/data-fetching-rules-for-server-components)
Your own site
<a href="https://agentmods.dev/rules/claire-gong-18/awesome-cursorrules/data-fetching-rules-for-server-components"><img src="https://agentmods.dev/badge/rules/claire-gong-18/awesome-cursorrules/data-fetching-rules-for-server-components/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.

agentmods 80×15 button for data-fetching-rules-for-server-components

Your own site · 80×15
<a href="https://agentmods.dev/rules/claire-gong-18/awesome-cursorrules/data-fetching-rules-for-server-components"><img src="https://agentmods.dev/badge/rules/claire-gong-18/awesome-cursorrules/data-fetching-rules-for-server-components.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 123 This file is loaded in full into every session.
When invoked 123 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.1 $0.00123 $0.00123
Opus 5 $0.00062 $0.00062
Sonnet 5 $0.00025 $0.00025
Haiku 4.5 $0.00012 $0.00012

Measured 5d ago against content hash bca59891e64a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

data-fetching-rules-for-server-components 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 5d 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.

Origin

This is a copy

100% identical to data-fetching-rules-for-server-components — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

rules/cursorrules-cursor-ai-nextjs-14-tailwind-seo-setup/data-fetching-rules-for-server-components.mdc · 15 lines

What it actually says

  • For data fetching in server components (in .tsx files): tsx async function getData() { const res = await fetch('https://api.example.com/data', { next: { revalidate: 3600 } }) if (!res.ok) throw new Error('Failed to fetch data') return res.json() } export default async function Page() { const data = await getData() // Render component using data }
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. 5d ago First seen · 15 lines · 123 tokens per session scan A bca59891e64a

Subscribe to this mod's changes

data-fetching-rules-for-server-components is a cursor rule published in the GitHub repository claire-gong-18/awesome-cursorrules (0 stars, last pushed 1y ago), licensed CC0-1.0. It adds 123 tokens to every session, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to data-fetching-rules-for-server-components, differing in 0 lines, and is treated as a copy.