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 t-code4change/nextjs-claude-skills --skill nextjs-cachinggit clone --depth 1 https://github.com/t-code4change/nextjs-claude-skillsWrote 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/t-code4change/nextjs-claude-skills/nextjs-caching)<a href="https://agentmods.dev/skills/t-code4change/nextjs-claude-skills/nextjs-caching"><img src="https://agentmods.dev/badge/skills/t-code4change/nextjs-claude-skills/nextjs-caching/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/t-code4change/nextjs-claude-skills/nextjs-caching"><img src="https://agentmods.dev/badge/skills/t-code4change/nextjs-claude-skills/nextjs-caching.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00071 | $0.01366 |
| Opus 5.5 | $0.00028 | $0.00546 |
| Sonnet 5.5 | $0.00014 | $0.00273 |
| Haiku 4.5 | $0.00007 | $0.00137 |
Grade A, and why
nextjs-caching 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next.js Caching (Cache Components)
Requires:
cacheComponents: trueinnext.config.ts(Next.js 16).
Project Detection
grep -r "cacheComponents" next.config.* 2>/dev/null
Enable
// next.config.ts
const nextConfig: NextConfig = { cacheComponents: true };
export default nextConfig;
Decision Steps
- Does component fetch data? No → skip. Yes → continue.
- Depends on
cookies()/headers()/searchParams? No → step 3. Yes → step 4. - Same data for all users? Yes →
'use cache'+cacheTag()+cacheLife(). No →<Suspense>. - Can extract runtime data as args? Yes → pass outside cache. No →
'use cache: private'(last resort).
Core APIs
'use cache' Directive
async function BlogPosts() {
'use cache'; // MUST be first statement; function MUST be async
cacheTag('posts');
cacheLife('hours');
return await db.posts.findMany();
}
cacheLife() Profiles
cacheLife('seconds'); // stale:30s | revalidate:1s | expire:1m
cacheLife('minutes'); // stale:5m | revalidate:1m | expire:1h
cacheLife('hours'); // stale:5m | revalidate:1h | expire:1d
cacheLife('days'); // stale:5m | revalidate:1d | expire:1w
cacheLife('weeks'); // stale:5m | revalidate:1w | expire:30d
cacheLife('max'); // stale:5m | revalidate:30d | expire:1y
// Custom:
cacheLife({ stale: 60, revalidate: 3600, expire: 86400 });
By content type: news → seconds, blog/docs → hours, marketing → days, legal → max
cacheTag() + Invalidation
// Tag
async function ProductList({ category }: { category: string }) {
'use cache';
cacheTag('products', `category-${category}`);
cacheLife('hours');
return await db.products.findMany({ where: { category } });
}
// Invalidate — Server Action (immediate, read-your-own-writes)
'use server';
export async function createProduct(formData: FormData): Promise<void> {
await db.products.create({ data: parseFormData(formData) });
updateTag('products');
}
// Invalidate — Route Handler / webhook (stale-while-revalidate)
export async function POST(request: Request) {
const { tag } = await request.json();
revalidateTag(tag, 'max'); // two-arg form — single arg is DEPRECATED
return Response.json({ revalidated: true });
}
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.
- 2mo ago First seen · 191 lines · 71 tokens per session scan A 89275acc805e
nextjs-caching is a skill published in the GitHub repository t-code4change/nextjs-claude-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 71 tokens to every session and 1,366 once invoked, about $0.0003 per session on Opus 5.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-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…