next-cache-components

next-cache-components is a skill for Claude Code, Codex from neverinfamous/memory-journal-mcp. It costs 99 tokens per session (2,852 once invoked), scanned A, original, MIT.

Guidance for Next.js 16's Cache Components, which can combine build-time content, cached data, and request-time content on one page. Next.js is a React framework for building web applications.

In plain words
What is it for?
Use it when applying caching directives, setting cache lifetimes or tags, using Partial Prerendering, or debugging static and dynamic React Server Components.
Why use it?
It helps decide which parts of a page should be generated once, reused for a period, or loaded fresh, while diagnosing related rendering issues. The feature may require a compatible Next.js canary version.

Skill for Claude CodeCodex

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 skills/neverinfamous/memory-journal-mcp/next-cache-components
Any agent
npx skills add neverinfamous/memory-journal-mcp --skill next-cache-components
Clone the repo
git clone --depth 1 https://github.com/neverinfamous/memory-journal-mcp

Made for: Claude Code, Codex.

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 next-cache-components

README.md
[![agentmods](https://agentmods.dev/badge/skills/neverinfamous/memory-journal-mcp/next-cache-components.svg)](https://agentmods.dev/skills/neverinfamous/memory-journal-mcp/next-cache-components)
Your own site
<a href="https://agentmods.dev/skills/neverinfamous/memory-journal-mcp/next-cache-components"><img src="https://agentmods.dev/badge/skills/neverinfamous/memory-journal-mcp/next-cache-components.svg" alt="Measured on agentmods" height="20"></a>
Per session 99 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,852 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.00099 $0.02852
Opus 5 $0.00049 $0.01426
Sonnet 5 $0.00020 $0.00570
Haiku 4.5 $0.00010 $0.00285

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

Security

Grade A, and why

next-cache-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.

skills/next-cache-components/SKILL.md · 442 lines

How it starts

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

Cache Components (Next.js 16+)

Note: Cache Components are available in Next.js canary. Verify cacheComponents is supported in your target version before applying this guidance.

Cache Components enable Partial Prerendering (PPR) - mix static, cached, and dynamic content in a single route.

Enable Cache Components

// next.config.ts
import type { NextConfig } from 'next'

const nextConfig: NextConfig = {
  cacheComponents: true,
}

export default nextConfig

This replaces the old experimental.ppr flag.


Three Content Types

With Cache Components enabled, content falls into three categories:

1. Static (Auto-Prerendered)

Synchronous code, imports, pure computations - prerendered at build time:

export default function Page() {
  return (
    <header>
      <h1>Our Blog</h1> {/* Static - instant */}
      <nav>...</nav>
    </header>
  )
}

2. Cached (use cache)

Async data that doesn't need fresh fetches every request:

async function BlogPosts() {
  'use cache'
  cacheLife('hours')

  const posts = await db.posts.findMany()
  return <PostList posts={posts} />
}

3. Dynamic (Suspense)

Runtime data that must be fresh - wrap in Suspense:

import { Suspense } from 'react'

export default function Page() {
  return (
    <>
      <BlogPosts /> {/* Cached */}
      <Suspense fallback={<p>Loading...</p>}>
        <UserPreferences /> {/* Dynamic - streams in */}
      </Suspense>
    </>
  )
}

async function UserPreferences() {
  const theme = (await cookies()).get('theme')?.value
  return <p>Theme: {theme}</p>
}

Selection Matrix: Static vs Cached vs Dynamic

When designing a component, use this matrix to determine the correct caching strategy:

Data Type Frequency of Change Strategy Implementation
Marketing copy, Layouts, Nav Build-time or rarely Static Default Server Component
Blog posts, Product catalog Periodic / CMS-driven Cached 'use cache' + cacheLife
User profile, Shopping cart Per-user / Real-time Dynamic Suspense + await cookies()
Admin dashboard, Analytics High-frequency / Secure Dynamic Suspense + await headers()

Read the full file on GitHub · 442 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 · 442 lines · 99 tokens per session scan A 16509a0bf284

Subscribe to this mod's changes

next-cache-components is a skill published in the GitHub repository neverinfamous/memory-journal-mcp (20 stars, last pushed 1mo ago), licensed MIT. It adds 99 tokens to every session and 2,852 once invoked, about $0.0005 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.