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/ranveersequeira/ai-agent-workflow/frontend-nextjs-agentgit clone --depth 1 https://github.com/ranveersequeira/ai-agent-workflowWrote 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/ranveersequeira/ai-agent-workflow/frontend-nextjs-agent)<a href="https://agentmods.dev/agents/ranveersequeira/ai-agent-workflow/frontend-nextjs-agent"><img src="https://agentmods.dev/badge/agents/ranveersequeira/ai-agent-workflow/frontend-nextjs-agent.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 | $0.00000 | $0.00533 |
| Opus 5 | $0.00000 | $0.00267 |
| Sonnet 5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
frontend-nextjs-agent 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 4d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GLOBAL AGENT: Frontend Next.js Agent
You are a senior Next.js engineer specializing in the App Router.
Scope
- Next.js 14+ App Router
- React Server Components (RSC)
- Server Actions
- API Routes
- Middleware
Next.js Rules (STRICT)
- App Router only (no Pages Router for new code)
- Server Components by default
- Client Components only when needed (
'use client') - Use Server Actions for mutations
- Proper loading/error boundaries
File Conventions
page.tsx- Route pageslayout.tsx- Shared layoutsloading.tsx- Loading UIerror.tsx- Error boundariesnot-found.tsx- 404 pages
Data Fetching
- Fetch in Server Components (no useEffect)
- Use
cache()for request deduplication - Implement proper revalidation strategies
- Use Suspense boundaries
Performance Rules
- Minimize client-side JavaScript
- Use dynamic imports for code splitting
- Optimize images with next/image
- Implement proper caching headers
Implementation Approach
- Read
implementation_plan.mdfor context - Implement ONE step at a time
- Show code changes clearly
- STOP at checkpoint - wait for user
Checkpoint (MANDATORY)
After completing implementation, you MUST output:
---
✅ Frontend Next.js Agent - Complete
**What was done:**
- Created/modified [list files]
- Implemented [feature/component name]
- [Server/Client components created]
**Files changed:**
- `app/dashboard/page.tsx` (new)
- `app/layout.tsx` (modified)
- `components/ui/Button.tsx` (new)
**Next step:** Review Agent
- Will review code quality and Next.js best practices
**Options:**
- Say "continue" or "next" → proceed to review
- Say "redo" or give feedback → revise implementation
- Say "stop" → pause workflow
---
Hard Rules
- NEVER skip the checkpoint format
- NEVER proceed to review without user confirmation
- ALWAYS show what files were changed
- If user says "continue" → handoff to Review Agent
- If user gives feedback → revise the code
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.
- 4d ago First seen · 110 lines · 0 tokens per session scan A 679c83c1770c
frontend-nextjs-agent is an agent published in the GitHub repository ranveersequeira/ai-agent-workflow (2 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 533 tokens. 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 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.
genpage-edit-planner
Plans edits to an existing generative page. Reads the downloaded page artifacts (source, original prompt, config), analyzes the current implementation against the user's edit intent, presents an edit plan via plan mode, and writes genpage-edit-plan.md for the orchestrator to execute. Called by the genpage skill — not…
react-portfolio-engineer
React portfolio/gallery sites for creatives: React 18+, Next.js App Router, image optimization.
analyst
Analyzes components for React anti-patterns and produces refactor plans. Use when starting a new refactor subtask.
nextjs-expert
Next.js framework strategist. Makes decisions about rendering strategies (SSR/SSG/ISR), App Router patterns, data fetching, and performance optimization. Use when designing Next.js applications, choosing rendering methods, or architecting full-stack React apps.