server-pages

A project rule for Next.js applications that makes files defining pages and layouts run on the server by default. Interactive parts belong in separate client-side component files.

In plain words
What is it for?
Use it when building pages under an app directory, especially when handling URL parameters or search fields. It also requires Suspense when certain child components read URL search parameters.
Why use it?
It prevents page and layout files from becoming client-side code unnecessarily and sets a consistent place for browser interactivity.

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/azacdev/knowledge-agent-template/server-pages
Clone the repo
git clone --depth 1 https://github.com/azacdev/knowledge-agent-template

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 141 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.00141
Opus 5 $0.00000 $0.00071
Sonnet 5 $0.00000 $0.00028
Haiku 4.5 $0.00000 $0.00014

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

Security

Grade A, and why

server-pages 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/server-pages.mdc · 15 lines

What it actually says

Server pages by default

Every app/**/page.tsx and app/**/layout.tsx must be a Server Component.

  • Do not add "use client" to pages or layouts.
  • Put interactivity in components/** client files and import them from the page.
  • Use Suspense on the server page when a child needs useSearchParams or similar.
  • Prefer async pages when you need params / searchParams.
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 · 15 lines · 0 tokens per session scan A 41fdb864ee12

Subscribe to this mod's changes

server-pages is a cursor rule published in the GitHub repository azacdev/knowledge-agent-template (2 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 141 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.