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/mertjane/awesome-claude-commandsWrote 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/mertjane/awesome-claude-commands/nxt-page)<a href="https://agentmods.dev/commands/mertjane/awesome-claude-commands/nxt-page"><img src="https://agentmods.dev/badge/commands/mertjane/awesome-claude-commands/nxt-page/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/commands/mertjane/awesome-claude-commands/nxt-page"><img src="https://agentmods.dev/badge/commands/mertjane/awesome-claude-commands/nxt-page.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.00040 | $0.01053 |
| Opus 5 | $0.00020 | $0.00526 |
| Sonnet 5 | $0.00008 | $0.00211 |
| Haiku 4.5 | $0.00004 | $0.00105 |
Grade A, and why
nxt-page 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 12d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Next.js Page
Create a complete Next.js App Router page set for the route provided in $ARGUMENTS.
Parse $ARGUMENTS as the route path (e.g. dashboard/settings, blog/[slug], shop/[category]/[id]).
Step 1 — Detect Project Structure
Check whether the project uses App Router or Pages Router:
- If
app/directory exists → App Router - If
pages/directory exists → Pages Router - If both exist → prefer App Router
If Pages Router is detected, stop and inform the user that this command supports App Router only.
Find the app directory root:
app/,src/app/
Step 2 — Analyze Existing Pages
Read 2–3 existing page.tsx files from the project:
Glob: {app,src/app}/**/page.tsx
Detect:
- Import patterns (aliased imports with
@/vs relative) - Whether pages use
asyncserver components - Whether pages pass
paramsandsearchParamsprops - Metadata pattern (
export const metadatavsgenerateMetadata) - Layout usage patterns
Step 3 — Parse Route Segments
Analyze the route path from $ARGUMENTS:
- Static segment:
dashboard→ folderdashboard/ - Dynamic segment:
[slug]→ folder[slug]/withparams.slug - Catch-all:
[...slug]→params.slugisstring[] - Optional catch-all:
[[...slug]]→params.slugisstring[] | undefined - Route groups:
(group)/route→ folder(group)/route/
Build the full output path: {app_root}/{route_path}/
Step 4 — Generate page.tsx
Generate an async Server Component:
import type { Metadata } from "next"
// Only include if dynamic params exist:
interface PageProps {
params: Promise<{ {param}: string }>
searchParams?: Promise<{ [key: string]: string | string[] | undefined }>
}
export const metadata: Metadata = {
title: "{Page Title}",
}
// With dynamic params:
export default async function {SegmentName}Page({ params }: PageProps) {
const { {param} } = await params
return (
<main className="container mx-auto px-4 py-8">
<h1 className="text-2xl font-bold">{Page Title}</h1>
</main>
)
}
// Without dynamic params:
export default async function {SegmentName}Page() {
return (
<main className="container mx-auto px-4 py-8">
<h1 className="text-2xl font-bold">{Page Title}</h1>
</main>
)
}
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.
- 12d ago First seen · 152 lines · 40 tokens per session scan A fa7ab7577284
nxt-page is a command published in the GitHub repository mertjane/awesome-claude-commands (2 stars, last pushed 6mo ago), licensed MIT. It adds 40 tokens to every session and 1,053 once invoked, about $0.0002 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
react-patterns
Review React code for performance and composition patterns — 50+ rules ranked by impact.
form-builder
Build accessible, validated forms with React Hook Form + Zod + shadcn Form, wired to a Next.js server action. Use when adding any form (contact, signup, chec...
review-component
Review a specific React component file using code-review-agent and frontend-development-agent. Analyze component architecture, proper Server vs Client component usage, prop types, hooks patterns (useState, useEffect, useCallback, useMemo), accessibility attributes (ARIA labels, semantic HTML, keyboard navigation)…
review-performance
Analyze application performance using code-review-agent and monitoring-observability-agent. Check Core Web Vitals (LCP < 2.5s, FID < 100ms, CLS < 0.1), bundle size analysis, image optimization (next/image, WebP format), font optimization (next/font), code splitting and lazy loading, caching strategies…
add-error-boundary
Implement React error boundaries throughout the application. Create error boundary component with componentDidCatch lifecycle. Add fallback UI with friendly error message and retry button. Log errors to monitoring service (Sentry, Azure Monitor) with stack traces. Implement granular boundaries for different sections…
migrate-to-nextjs15
Upgrade this Next.js project to version 15. Update package.json dependencies to Next.js 15 and React 19. Migrate App Router patterns and update metadata API usage following latest conventions. Fix breaking changes in configuration, middleware, and API routes. Update next.config.ts with new configuration options. Test…