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.
npx skills add robotostudio/turbo-start-sanity --skill next-cache-componentsgit clone --depth 1 https://github.com/robotostudio/turbo-start-sanityWrote 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.
[](https://agentmods.dev/skills/robotostudio/turbo-start-sanity/next-cache-components)<a href="https://agentmods.dev/skills/robotostudio/turbo-start-sanity/next-cache-components"><img src="https://agentmods.dev/badge/skills/robotostudio/turbo-start-sanity/next-cache-components/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/robotostudio/turbo-start-sanity/next-cache-components"><img src="https://agentmods.dev/badge/skills/robotostudio/turbo-start-sanity/next-cache-components.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00026 | $0.02380 |
| Opus 5 | $0.00013 | $0.01190 |
| Sonnet 5 | $0.00005 | $0.00476 |
| Haiku 4.5 | $0.00003 | $0.00238 |
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 10d 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.
Copies of this mod
6 near-identical copies found in the catalogue:
- next-cache-components — 100% identical, 230 lines differ
- next-cache-components — 100% identical, 230 lines differ
- next-cache-components — 100% identical, 26 lines differ
- next-cache-components — 100% identical, 230 lines differ
- next-cache-components — 100% identical, 120 lines differ
- next-cache-components — 88% identical, 308 lines differ
How it starts
The opening of the file, as written. The whole thing — 424 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
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.
- 10d ago First seen · 424 lines · 26 tokens per session scan A 5481b481f7b9
next-cache-components is a skill published in the GitHub repository robotostudio/turbo-start-sanity (176 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 2,380 once invoked, about $0.0001 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.
Other skills, from other repositories
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit calls, or resolve the link-prefetch-partial and instant-shell-url-data…
sanity-live-cache-components
Integrates Sanity Live with Next.js Cache Components in next-sanity v13+ apps. Sets up sanityFetch, a shared cachedSanity 'use cache' boundary, , Visual Editing, Presentation Tool, draft mode handling, and the three-layer (Page/Dynamic/Cached) component pattern with explicit perspective/stega prop-drilling. Sequences…
pnpm
Node.js package manager with strict dependency resolution. Use when running pnpm specific commands, configuring workspaces, or managing dependencies with catalogs, patches, or overrides.
gcss-v3-site-framework
Initialize, adapt, audit, upgrade, or downgrade projects built from gcss-v3-site-framework. Use for A1/A2/B/C delivery profiles, static-brand/cms-brand/retail setup, Astro and Sanity page models, the C Retail Catalog & Content Foundation with read-only Shopify catalog mapping, Cloudflare Worker routes, project…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance…