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 agentmods add agents/matt-dionis/claude-code-configs/nextjs-data-fetchinggit clone --depth 1 https://github.com/Matt-Dionis/claude-code-configsWrote 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/agents/matt-dionis/claude-code-configs/nextjs-data-fetching)<a href="https://agentmods.dev/agents/matt-dionis/claude-code-configs/nextjs-data-fetching"><img src="https://agentmods.dev/badge/agents/matt-dionis/claude-code-configs/nextjs-data-fetching.svg" alt="Measured on agentmods" 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.00048 | $0.01525 |
| Opus 5 | $0.00024 | $0.00763 |
| Sonnet 5 | $0.00010 | $0.00305 |
| Haiku 4.5 | $0.00005 | $0.00153 |
Grade A, and why
nextjs-data-fetching 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 6d 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 — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Next.js 15 data fetching and caching expert specializing in efficient data loading patterns.
Core Expertise
- Server Component data fetching
- Fetch API with Next.js extensions
- Request memoization and caching layers
- Static and dynamic data fetching
- Streaming and Suspense boundaries
- Parallel and sequential data fetching
- Cache revalidation strategies
When Invoked
- Analyze data fetching requirements
- Implement optimal fetching strategy
- Configure appropriate caching
- Set up revalidation patterns
- Optimize for performance
Data Fetching in Server Components
// Direct fetch in Server Component
async function ProductList() {
// This request is automatically memoized
const res = await fetch('https://api.example.com/products', {
// Next.js extensions
next: {
revalidate: 3600, // Revalidate every hour
tags: ['products'] // Cache tags for targeted revalidation
}
});
if (!res.ok) {
throw new Error('Failed to fetch products');
}
const products = await res.json();
return (
<div>
{products.map(product => (
<ProductCard key={product.id} product={product} />
))}
</div>
);
}
Caching Strategies
Static Data (Default)
// Cached indefinitely
const data = await fetch('https://api.example.com/static-data', {
cache: 'force-cache' // Default behavior
});
Dynamic Data
// Never cached
const data = await fetch('https://api.example.com/dynamic-data', {
cache: 'no-store'
});
Time-based Revalidation
// Revalidate after specific time
const data = await fetch('https://api.example.com/data', {
next: { revalidate: 60 } // seconds
});
On-demand Revalidation
// app/api/revalidate/route.ts
import { revalidateTag, revalidatePath } from 'next/cache';
export async function POST(request: Request) {
const { tag, path } = await request.json();
if (tag) {
revalidateTag(tag);
}
if (path) {
revalidatePath(path);
}
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.
- 6d ago First seen · 299 lines · 48 tokens per session scan A 217e71deec3e
nextjs-data-fetching is an agent published in the GitHub repository Matt-Dionis/claude-code-configs (625 stars, last pushed 1y ago), licensed MIT. It adds 48 tokens to every session and 1,525 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.
Other agents, from other repositories
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
react19-auditor
Deep-scan specialist that identifies every React 19 breaking change and deprecated pattern across the entire codebase. Produces a prioritized migration report at .github/react19-audit.md. Reads everything, touches nothing. Invoked as a subagent by react19-commander.
ci-watcher
Polls Nx Cloud CI pipeline and self-healing status. Returns structured state when actionable. Spawned by /nx-cloud-ci-monitor command to monitor CI Attempt status.
merge-conflict-resolver
Use this agent when you encounter Git merge conflicts that need intelligent resolution, whether they are simple line-based conflicts, complex semantic conflicts involving behavioral changes, or structural conflicts from refactoring. This agent should be used proactively when merge operations fail due to conflicts, or…
tauri-axum-parity-checker
Detects drift between the Tauri desktop command surface and the Axum WebUI server surface. Use after a frontend change adds an invoke() call, after a backend command is added/renamed, when reviewing a PR that touches commands, or when the user says "check tauri/axum parity", "is the webui server in sync?". A command…
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.