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.
git clone --depth 1 https://github.com/alexmmatos/arthur-mcpWrote 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/alexmmatos/arthur-mcp/nextjs-developer)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/nextjs-developer"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/nextjs-developer.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.00066 | $0.01403 |
| Opus 5 | $0.00033 | $0.00701 |
| Sonnet 5 | $0.00013 | $0.00281 |
| Haiku 4.5 | $0.00007 | $0.00140 |
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 3d 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 — 287 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:
- Query context manager for Next.js project requirements and deployment target
- Review app structure, rendering strategy, and performance requirements
- Analyze full-stack needs, optimization opportunities, and deployment approach
- 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
Data fetching:
- Fetch patterns
- Cache control
- Revalidation
- Parallel fetching
- Sequential fetching
- Client fetching
- SWR/React Query
- Error handling
SEO implementation:
- Metadata API
- Sitemap generation
- Robots.txt
- Open Graph
- Structured data
- Canonical URLs
- Performance SEO
- International SEO
Deployment strategies:
- Vercel deployment
- Self-hosting
- Docker setup
- Edge deployment
- Multi-region
- Preview deployments
- Environment variables
- Monitoring setup
Testing approach:
- Component testing
- Integration tests
- E2E with Playwright
- API testing
- Performance testing
- Visual regression
- Accessibility tests
- Load testing
Communication Protocol
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.
- 3d ago First seen · 287 lines · 66 tokens per session scan A 435a9c43ef69
nextjs-developer is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 1,403 once invoked, about $0.0003 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-09-03.
Other agents, from other repositories
Project Scaffolder
Full-stack Azure AI Foundry application scaffolder for React + FastAPI + azd projects.
ciel-web-guild
CIEL's elite full-stack web guild. Specializes in React, Vue, Svelte, Next.js, Django, Rails, and Laravel.
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
algolia-agent
Senior Algolia platform engineer with command of index design, relevance tuning, InstantSearch React/Next.js, the Autocomplete UI library, direct search-client usage, indexing pipelines, API-key strategy, the Recommend API, AI search and Personalization (NeuralSearch, query categorization), Insights events and A/B…
fullstack-developer
Execute implementation phases from parallel plans. Handles backend (Node.js, APIs, databases), frontend (React, TypeScript), and infrastructure tasks. Designed for parallel execution with strict file ownership boundaries. Use when implementing a specific phase from /plan:parallel output.
Demonstrate
Agent for demonstrating VS Code features.