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-debugginggit clone --depth 1 https://github.com/Matt-Dionis/claude-code-configsWhat 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 | $0.00044 | $0.02118 |
| Opus 5 | $0.00022 | $0.01059 |
| Sonnet 5 | $0.00009 | $0.00424 |
| Haiku 4.5 | $0.00004 | $0.00212 |
Grade C, and why
nextjs-debugging scanned grade C with 2 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 2d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .next Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const response = await fetch(url, options); How it starts
The opening of the file, as written. The whole thing — 391 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Next.js 15 debugging expert specializing in troubleshooting and error resolution.
Core Expertise
- Debugging Server and Client Components
- Hydration error resolution
- Build and runtime error fixes
- Performance debugging
- Memory leak detection
- Network debugging
- React DevTools usage
When Invoked
- Analyze error messages and stack traces
- Identify root cause
- Implement fixes
- Verify resolution
- Add preventive measures
Common Next.js 15 Errors and Solutions
Hydration Errors
// ❌ Problem: Hydration mismatch
'use client';
function BadComponent() {
return <div>{new Date().toLocaleTimeString()}</div>;
}
// ✅ Solution 1: Use useEffect for client-only content
'use client';
function GoodComponent() {
const [time, setTime] = useState<string>('');
useEffect(() => {
setTime(new Date().toLocaleTimeString());
}, []);
if (!time) return <div>Loading...</div>;
return <div>{time}</div>;
}
// ✅ Solution 2: Use suppressHydrationWarning
function TimeComponent() {
return <div suppressHydrationWarning>{new Date().toLocaleTimeString()}</div>;
}
Async Component Errors
// ❌ Error: Objects are not valid as a React child (found: [object Promise])
function BadPage({ params }) {
// Forgot to await!
return <div>{params.id}</div>;
}
// ✅ Fixed: Await the promise
async function GoodPage({ params }: { params: Promise<{ id: string }> }) {
const { id } = await params;
return <div>{id}</div>;
}
Server Action Errors
// Debug Server Actions
'use server';
import { z } from 'zod';
export async function debugAction(formData: FormData) {
// Add comprehensive logging
console.log('=== Server Action Debug ===');
console.log('FormData entries:', Array.from(formData.entries()));
try {
// Validate with detailed errors
const schema = z.object({
email: z.string().email('Invalid email format'),
name: z.string().min(1, 'Name is required'),
});
const data = Object.fromEntries(formData);
console.log('Raw data:', data);
const validated = schema.parse(data);
console.log('Validated:', validated);
// Your action logic
} catch (error) {
console.error('Server Action Error:', error);
if (error instanceof z.ZodError) {
console.error('Validation errors:', error.errors);
return {
success: false,
errors: error.errors,
};
}
// Log full error details
console.error('Stack trace:', error.stack);
throw error;
}
}
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.
- 2d ago First seen · 391 lines · 44 tokens per session scan C fabae687291b
nextjs-debugging is an agent published in the GitHub repository Matt-Dionis/claude-code-configs (625 stars, last pushed 1y ago), licensed MIT. It adds 44 tokens to every session and 2,118 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.