data-fetching-rules-for-server-components

data-fetching-rules-for-server-components is a cursor rule for Cursor from holtwood/awesome-cursorrules-zh. It costs 0 tokens per session (127 once invoked), scanned A, original, MIT.

A set of rules for fetching data inside Next.js 14 server components, which render on the server rather than in the browser.

In plain words
What is it for?
Use it when building Next.js pages that load data from an API in server-rendered React components.
Why use it?
It provides a consistent way to call an API, handle failed responses, and reuse cached results for a set period.

Cursor rule for Cursor

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

Good fit Use it when building Next.js pages that load data from an API…

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/holtwood/awesome-cursorrules-zh/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/holtwood/awesome-cursorrules-zh

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/holtwood/awesome-cursorrules-zh/data-fetching-rules-for-server-components.svg)](https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/data-fetching-rules-for-server-components)
Your own site
<a href="https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/data-fetching-rules-for-server-components"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/data-fetching-rules-for-server-components.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 127 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.00127
Opus 5 $0.00000 $0.00063
Sonnet 5 $0.00000 $0.00025
Haiku 4.5 $0.00000 $0.00013

Measured 3d ago against content hash 933ae6b6e1ce, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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 3d 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.

docs/rules/frontend/react/nextjs-14-seo/data-fetching-rules-for-server-components.mdc · 17 lines

What it actually says

  • 对于服务器组件中的数据获取(在 .tsx 文件中):
    async function getData() {
      const res = await fetch('https://api.example.com/data', { next: { revalidate: 3600 } })
      if (!res.ok) throw new Error('获取数据失败')
      return res.json()
    }
    export default async function Page() {
      const data = await getData()
      // 使用数据渲染组件
    }
    
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. 3d ago First seen · 17 lines · 127 tokens per session scan A 933ae6b6e1ce

Subscribe to this mod's changes

data-fetching-rules-for-server-components is a cursor rule published in the GitHub repository holtwood/awesome-cursorrules-zh (232 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 127 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-09-03.