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 skills add Shiven0504/claude-skills-collection --skill nextjs-architectgit clone --depth 1 https://github.com/Shiven0504/claude-skills-collectionWrote 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/skills/shiven0504/claude-skills-collection/nextjs-architect)<a href="https://agentmods.dev/skills/shiven0504/claude-skills-collection/nextjs-architect"><img src="https://agentmods.dev/badge/skills/shiven0504/claude-skills-collection/nextjs-architect/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/skills/shiven0504/claude-skills-collection/nextjs-architect"><img src="https://agentmods.dev/badge/skills/shiven0504/claude-skills-collection/nextjs-architect.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.00103 | $0.02259 |
| Opus 5 | $0.00051 | $0.01130 |
| Sonnet 5 | $0.00021 | $0.00452 |
| Haiku 4.5 | $0.00010 | $0.00226 |
Grade A, and why
nextjs-architect 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 11d 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 — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next.js App Router Architecture
Help users make sound architectural decisions in Next.js App Router projects using Tailwind CSS for styling.
Server vs Client Components
The most important architectural decision in modern Next.js is understanding the server/client boundary.
Default to Server Components
Every component is a Server Component unless it opts in with "use client". Keep components on the server when they:
- Fetch data (database queries, API calls)
- Access backend resources directly
- Keep sensitive logic (tokens, API keys) off the client
- Render large dependencies that don't need interactivity
Use Client Components when you need
- Event handlers (onClick, onChange, onSubmit)
- State (useState, useReducer)
- Effects (useEffect, useLayoutEffect)
- Browser APIs (window, document, localStorage)
- Custom hooks that depend on state or effects
The boundary pattern
Push "use client" as far down the tree as possible. Instead of making an entire page a client component because one button needs state, extract just the interactive part:
app/
dashboard/
page.tsx ← Server Component (fetches data)
components/
stats-grid.tsx ← Server Component (renders data)
filter-bar.tsx ← Client Component (has state)
Example — composing server and client:
// app/dashboard/page.tsx (Server Component)
import { FilterBar } from './components/filter-bar'
import { StatsGrid } from './components/stats-grid'
export default async function DashboardPage() {
const stats = await getStats()
return (
<div className="p-6">
<FilterBar />
<StatsGrid data={stats} />
</div>
)
}
// app/dashboard/components/filter-bar.tsx
"use client"
import { useState } from 'react'
export function FilterBar() {
const [filter, setFilter] = useState('all')
return (
<div className="flex gap-2 mb-4">
{['all', 'active', 'archived'].map(f => (
<button
key={f}
onClick={() => setFilter(f)}
className={`px-3 py-1 rounded ${filter === f ? 'bg-blue-600 text-white' : 'bg-gray-100'}`}
>
{f}
</button>
))}
</div>
)
}
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.
- 11d ago First seen · 339 lines · 103 tokens per session scan A 2a1904b7dd68
nextjs-architect is a skill published in the GitHub repository Shiven0504/claude-skills-collection (6 stars, last pushed 5mo ago), licensed MIT. It adds 103 tokens to every session and 2,259 once invoked, about $0.0005 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 skills, from other repositories
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
menu-transitions-rtl
Animate react-horizontal-scrolling-menu scrolling and build right-to-left menus: noPolyfill defaults to true since v8, so transitionDuration (default 500), a custom-easing-function transitionBehavior, and per-call ScrollOptions { duration, boundary } on scrollToItem/scrollNext/scrollPrev are silently ignored unless…