next-cache-components

next-cache-components is a skill for Claude Code, Codex from figueroaignacio/ignaciofigueroa.dev. It costs 26 tokens per session (2,363 once invoked), scanned A, a copy of next-cache-components, MIT.

A guide to Cache Components in Next.js 16, a framework for building React websites. It explains how pages can combine build-time content, cached data, and fresh request-time data.

In plain words
What is it for?
Use it when configuring Next.js 16 caching, partial prerendering, cached database or API data, dynamic content, cache lifetimes, or cache tags.
Why use it?
It helps control which parts of a page should be fast and reusable and which parts must stay current. It also explains the settings and code patterns needed for this behavior.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it when configuring Next.js 16 caching, partial prerendering, cached database or API data, dynamic content, cache lifetimes, or cache tags.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/figueroaignacio/ignaciofigueroa.dev/next-cache-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.

Any agent
npx skills add figueroaignacio/ignaciofigueroa.dev --skill next-cache-components
Clone the repo
git clone --depth 1 https://github.com/figueroaignacio/ignaciofigueroa.dev

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/figueroaignacio/ignaciofigueroa.dev/next-cache-components.svg)](https://agentmods.dev/skills/figueroaignacio/ignaciofigueroa.dev/next-cache-components)
Your own site
<a href="https://agentmods.dev/skills/figueroaignacio/ignaciofigueroa.dev/next-cache-components"><img src="https://agentmods.dev/badge/skills/figueroaignacio/ignaciofigueroa.dev/next-cache-components.svg" alt="Measured on agentmods" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,363 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 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.00026 $0.02363
Opus 5 $0.00013 $0.01182
Sonnet 5 $0.00005 $0.00473
Haiku 4.5 $0.00003 $0.00236

Measured 8d ago against content hash 38215dce9194, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, 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 8d 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 next-cache-components — 120 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.

.agents/skills/next-cache-components/SKILL.md · 412 lines

How it starts

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

Cache Components (Next.js 16+)

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>;
}

use cache Directive

File Level

'use cache';

export default async function Page() {
  // Entire page is cached
  const data = await fetchData();
  return <div>{data}</div>;
}

Component Level

export async function CachedComponent() {
  'use cache';
  const data = await fetchData();
  return <div>{data}</div>;
}

Function Level

export async function getData() {
  'use cache';
  return db.query('SELECT * FROM posts');
}

Cache Profiles

Built-in Profiles

Read the full file on GitHub · 412 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. 8d ago First seen · 412 lines · 26 tokens per session scan A 38215dce9194

Subscribe to this mod's changes

next-cache-components is a skill published in the GitHub repository figueroaignacio/ignaciofigueroa.dev (5 stars, last pushed 4d ago), licensed MIT. It adds 26 tokens to every session and 2,363 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to next-cache-components, differing in 120 lines, and is treated as a copy.

Related

Other skills, from other repositories

web-artifacts-builder

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

ThinkInAIXYZ/deepchat · 64 tokens

frontend-code-review

Trigger when the user requests a review of frontend files (e.g., .tsx, .ts, .js). Support both pending-change reviews and focused file reviews while applying the checklist rules.

sangrokjung/claude-forge · 42 tokens

panel-app-react-vite-creator

Create or update an engineering-style NextClaw Panel component with pnpm, Vite, React, TypeScript, and Tailwind CSS, then build it into a static .panel directory inside a schema v2 package or an explicitly loose workspace Panel. Use for modern, reusable, complex, Agent-powered, typed Panel interfaces.

Peiiii/nextclaw · 73 tokens

react-form-validator

This skill should be used when the user asks to "create a form", "add validation", "handle form submission", "use React Hook Form", or when creating login, signup, or data entry forms. Enforces React Hook Form + Zod pattern.

smicolon/ai-kit · 56 tokens

TanStack Table Patterns

Auto-enforce TanStack Table best practices for headless data tables. Activates when creating tables, implementing sorting, filtering, pagination, or building data grids in React applications.

smicolon/ai-kit · 40 tokens

TanStack Virtual Patterns

Auto-enforce TanStack Virtual best practices for list virtualization. Activates when implementing large lists, infinite scroll, virtualized grids, or performance optimization for long lists in React applications.

smicolon/ai-kit · 41 tokens