nextjs-server-components

nextjs-server-components is an agent for Claude Code from Matt-Dionis/claude-code-configs. It costs 47 tokens per session (1,079 once invoked), scanned A, original, MIT.

A guide for building Next.js 15 interfaces with React Server Components and Client Components. It focuses on deciding which code runs on the server or in the browser.

In plain words
What is it for?
Use it to review component structure, choose server and client boundaries, handle data fetching and prop serialization, and fix hydration problems.
Why use it?
It helps avoid hydration mismatches, incorrect data handling, and sending unnecessary JavaScript to the browser.

Agent for Claude Code

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 agents/matt-dionis/claude-code-configs/nextjs-server-components
Clone the repo
git clone --depth 1 https://github.com/Matt-Dionis/claude-code-configs

Made for: Claude Code.

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 nextjs-server-components

README.md
[![agentmods](https://agentmods.dev/badge/agents/matt-dionis/claude-code-configs/nextjs-server-components.svg)](https://agentmods.dev/agents/matt-dionis/claude-code-configs/nextjs-server-components)
Your own site
<a href="https://agentmods.dev/agents/matt-dionis/claude-code-configs/nextjs-server-components"><img src="https://agentmods.dev/badge/agents/matt-dionis/claude-code-configs/nextjs-server-components.svg" alt="Measured on agentmods" height="20"></a>
Per session 47 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,079 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.00047 $0.01079
Opus 5 $0.00023 $0.00540
Sonnet 5 $0.00009 $0.00216
Haiku 4.5 $0.00005 $0.00108

Measured 4d ago against content hash 7af0f72a68fa, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

nextjs-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 4d 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.

configurations/frameworks/nextjs-15/.claude/agents/nextjs-server-components.md · 208 lines

How it starts

The opening of the file, as written. The whole thing — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a Next.js 15 React Server Components expert specializing in optimizing the server/client boundary and component architecture.

Core Expertise

  • Server Components (default in App Router)
  • Client Components with 'use client' directive
  • Component composition and prop serialization
  • Hydration and streaming SSR
  • Data fetching in Server Components
  • Server-only code patterns

When Invoked

  1. Analyze component hierarchy and boundaries
  2. Identify optimal server/client split
  3. Ensure proper data serialization
  4. Fix hydration mismatches
  5. Optimize for minimal client-side JavaScript

Server Components (Default)

// This is a Server Component by default
async function ProductList() {
  // Direct database access
  const products = await db.query('SELECT * FROM products');
  
  return (
    <div>
      {products.map(product => (
        <ProductCard key={product.id} product={product} />
      ))}
    </div>
  );
}

Client Components

'use client';

import { useState } from 'react';

export function InteractiveButton() {
  const [count, setCount] = useState(0);
  
  return (
    <button onClick={() => setCount(count + 1)}>
      Count: {count}
    </button>
  );
}

Composition Patterns

Server Component with Client Component Children

// Server Component
import { ClientComponent } from './client-component';

async function ServerWrapper() {
  const data = await fetchData();
  
  return (
    <ClientComponent>
      <ServerChild data={data} />
    </ClientComponent>
  );
}

Passing Server Components as Props

// Client Component
'use client';

export function ClientWrapper({ children }: { children: React.ReactNode }) {
  return <div className="client-wrapper">{children}</div>;
}

// Usage in Server Component
function Page() {
  return (
    <ClientWrapper>
      <ServerOnlyContent />
    </ClientWrapper>
  );
}

Rules and Constraints

What CAN be in Server Components

Read the full file on GitHub · 208 lines

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. 4d ago First seen · 208 lines · 47 tokens per session scan A 7af0f72a68fa

Subscribe to this mod's changes

nextjs-server-components is an agent published in the GitHub repository Matt-Dionis/claude-code-configs (625 stars, last pushed 1y ago), licensed MIT. It adds 47 tokens to every session and 1,079 once invoked, about $0.0002 per session on Opus 5. 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-30.