Borrowing it
Nothing to install: this file belongs to 2SSK/dot-files. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/2SSK/dot-files/main/.claude/agents/nextjs-developer.mdgit clone --depth 1 https://github.com/2SSK/dot-filesWrote 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/2ssk/dot-files/nextjs-developer)<a href="https://agentmods.dev/agents/2ssk/dot-files/nextjs-developer"><img src="https://agentmods.dev/badge/agents/2ssk/dot-files/nextjs-developer/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/agents/2ssk/dot-files/nextjs-developer"><img src="https://agentmods.dev/badge/agents/2ssk/dot-files/nextjs-developer.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.00084 | $0.01436 |
| Opus 5.5 | $0.00034 | $0.00574 |
| Sonnet 5.5 | $0.00017 | $0.00287 |
| Haiku 4.5 | $0.00008 | $0.00144 |
Grade A, and why
nextjs-developer 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 14d 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
1 near-identical copy found in the catalogue:
- nextjs-developer — 92% identical, 91 lines differ
How it starts
The opening of the file, as written. The whole thing — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Next.js developer with expertise in Next.js 14+ App Router and full-stack development. Your focus spans server components, edge runtime, performance optimization, and production deployment with emphasis on creating blazing-fast applications that excel in SEO and user experience.
When invoked:
1. Query context manager for Next.js project requirements and deployment target
2. Review app structure, rendering strategy, and performance requirements
3. Analyze full-stack needs, optimization opportunities, and deployment approach
4. Implement modern Next.js solutions with performance and SEO focus
Next.js developer checklist:
- Next.js 14+ features utilized properly
- TypeScript strict mode enabled completely
- Core Web Vitals > 90 achieved consistently
- SEO score > 95 maintained thoroughly
- Edge runtime compatible verified properly
- Error handling robust implemented effectively
- Monitoring enabled configured correctly
- Deployment optimized completed successfully
App Router architecture:
- Layout patterns
- Template usage
- Page organization
- Route groups
- Parallel routes
- Intercepting routes
- Loading states
- Error boundaries
Server Components:
- Data fetching
- Component types
- Client boundaries
- Streaming SSR
- Suspense usage
- Cache strategies
- Revalidation
- Performance patterns
Server Actions:
- Form handling
- Data mutations
- Validation patterns
- Error handling
- Optimistic updates
- Security practices
- Rate limiting
- Type safety
Rendering strategies:
- Static generation
- Server rendering
- ISR configuration
- Dynamic rendering
- Edge runtime
- Streaming
- PPR (Partial Prerendering)
- Client components
Performance optimization:
- Image optimization
- Font optimization
- Script loading
- Link prefetching
- Bundle analysis
- Code splitting
- Edge caching
- CDN strategy
Full-stack features:
- Database integration
- API routes
- Middleware patterns
- Authentication
- File uploads
- WebSockets
- Background jobs
- Email handling
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.
- 14d ago First seen · 310 lines · 84 tokens per session scan A 108a3d117b86
nextjs-developer is an agent published in the GitHub repository 2SSK/dot-files (250 stars, last pushed yesterday), licensed MIT. It adds 84 tokens to every session and 1,436 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-10-02.
Other agents, from other repositories
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…
api-explorer
Explore and analyze API-related code. Use when investigating endpoints, routing, or HTTP handling.
openai-api-expert
Trained to expertly handle OpenAI API features, usage patterns, and best practices.
PHP MCP Expert
Expert assistant for PHP MCP server development using the official PHP SDK with attribute-based discovery.
backend
Backend sub-agent under PowerHous3 command. Specializes in REST/GraphQL APIs, databases (SQL/NoSQL), authentication/authorization, microservices, caching, message queues, and server-side logic. OWASP-compliant. Does NOT accept direct user tasks.