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 commands/rcdelacruz/claude-code-agents/workflow-design-nextjsgit clone --depth 1 https://github.com/rcdelacruz/claude-code-agentsWrote 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/commands/rcdelacruz/claude-code-agents/workflow-design-nextjs)<a href="https://agentmods.dev/commands/rcdelacruz/claude-code-agents/workflow-design-nextjs"><img src="https://agentmods.dev/badge/commands/rcdelacruz/claude-code-agents/workflow-design-nextjs.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.00008 | $0.00694 |
| Opus 5 | $0.00004 | $0.00347 |
| Sonnet 5 | $0.00002 | $0.00139 |
| Haiku 4.5 | $0.00001 | $0.00069 |
Grade A, and why
workflow-design-nextjs 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are in NEXT.JS DESIGN MODE.
Use the fullstack-js-savant agent to design a modern Next.js application architecture.
Design Workflow
1. Application Structure Design
- App Router Layout: Design layout hierarchy and nested routes
- Server vs Client Components: Plan which components should be Server/Client
- Data Fetching Strategy: Determine where to fetch data (Server Components, Route Handlers, Server Actions)
- Streaming Strategy: Plan Suspense boundaries and loading states
2. Routing Architecture
app/
├── (auth)/
│ ├── login/
│ └── signup/
├── (dashboard)/
│ ├── layout.tsx (protected layout)
│ ├── page.tsx
│ └── [features]/
└── api/
├── trpc/
└── webhooks/
3. State Management Design
- Server State: React Query/TanStack Query configuration
- Client State: Zustand, Jotai, or Context API
- Form State: react-hook-form with Zod schemas
- URL State: searchParams for filters and pagination
4. API Layer Design
- tRPC Setup: Define routers and procedures
- Route Handlers: REST endpoints for webhooks, third-party integrations
- Server Actions: Form submissions, mutations
- Middleware: Authentication, rate limiting, logging
5. Database Integration
- Prisma Schema: Design entities and relationships
- Query Patterns: Plan data fetching patterns to avoid N+1 queries
- Caching: Redis for session, query results, rate limiting
6. Authentication Flow
- NextAuth.js v5: Configure providers, callbacks, session strategy
- Protected Routes: Middleware vs layout-based protection
- Authorization: Role-based access control (RBAC)
7. UI Component Strategy
- shadcn/ui Components: Which components to install
- Custom Components: Shared UI components structure
- Theme System: Dark mode, color schemes, typography
8. Performance Planning
- Bundle Optimization: Code splitting strategy, dynamic imports
- Image Optimization: next/image usage patterns
- Font Optimization: next/font configuration
- Caching Headers: ISR, SSG, dynamic rendering decisions
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 · 91 lines · 8 tokens per session scan A a4ee6e67caf8
workflow-design-nextjs is a command published in the GitHub repository rcdelacruz/claude-code-agents (2 stars, last pushed 10mo ago), licensed MIT. It adds 8 tokens to every session and 694 once invoked, about $0.0000 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.