create-page

create-page is a command for Claude Code from armanzeroeight/fastagent-plugins. It costs 13 tokens per session (814 once invoked), scanned A, original, MIT.

A command for creating a new page in a Next.js application. It detects whether the project uses the App Router or the older Pages Router and creates the matching files.

In plain words
What is it for?
Use it to add ordinary or dynamic routes, create the required directories and page component, and choose server-side rendering, static generation, or incremental regeneration.
Why use it?
It removes repetitive setup work and helps new pages use an explicitly chosen rendering method.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: positional $N argument.

Good fit Use it to add ordinary or dynamic routes, create the required directories and page component, and choose server-side rendering, static generation, or incremental regeneration.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/armanzeroeight/fastagent-plugins/create-page
Install

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.

Clone the repo
git clone --depth 1 https://github.com/armanzeroeight/fastagent-plugins

Made for: Claude Code.

Wrote 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.

agentmods badge for create-page

README.md
[![agentmods](https://agentmods.dev/badge/commands/armanzeroeight/fastagent-plugins/create-page/github.svg)](https://agentmods.dev/commands/armanzeroeight/fastagent-plugins/create-page)
Your own site
<a href="https://agentmods.dev/commands/armanzeroeight/fastagent-plugins/create-page"><img src="https://agentmods.dev/badge/commands/armanzeroeight/fastagent-plugins/create-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.

agentmods 80×15 button for create-page

Your own site · 80×15
<a href="https://agentmods.dev/commands/armanzeroeight/fastagent-plugins/create-page"><img src="https://agentmods.dev/badge/commands/armanzeroeight/fastagent-plugins/create-page.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 814 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00013 $0.00814
Opus 5.5 $0.00005 $0.00326
Sonnet 5.5 $0.00003 $0.00163
Haiku 4.5 $0.00001 $0.00081

Measured 1mo ago against content hash 04f9ac2e68f3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-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 1mo 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.

plugins/nextjs-toolkit/commands/create-page.md · 132 lines

How it starts

The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create Page

Generate a new Next.js page with the appropriate rendering strategy.

Context

  • Current directory: !pwd
  • Next.js version: !cat package.json | grep '"next"' || echo "Not found"
  • App Router: ![ -d "app" ] && echo "Yes" || echo "No"

Your Task

Create a new Next.js page with proper structure and rendering strategy.

Arguments

  • $1: Page path (e.g., "products/[id]", "blog", "dashboard")
  • $2: Optional flag for rendering strategy:
    • --ssr: Server-Side Rendering
    • --ssg: Static Site Generation
    • --isr: Incremental Static Regeneration
    • (default: SSG for App Router, SSG for Pages Router)

Steps

  1. Detect Next.js structure

    • Check if using App Router (app/ directory) or Pages Router (pages/ directory)
    • Determine Next.js version from package.json
  2. Parse page path

    • Extract route segments
    • Identify dynamic segments ([id], [...slug])
    • Determine if nested route
  3. Create directory structure

    • For App Router: app/<path>/page.tsx
    • For Pages Router: pages/<path>.tsx or pages/<path>/index.tsx
    • Create parent directories as needed
  4. Generate page component

    For App Router:

    • Server Component by default
    • Add 'use client' if interactive
    • Include metadata export
    • Add loading.tsx and error.tsx if appropriate

    For Pages Router:

    • Add getStaticProps for SSG/ISR
    • Add getServerSideProps for SSR
    • Add getStaticPaths for dynamic routes
  5. Add TypeScript types

    • Props interface
    • Params type for dynamic routes
    • Metadata type for App Router
  6. Provide usage instructions

    • How to navigate to the page
    • How to pass data
    • How to customize rendering
    • Next steps for implementation

Output Format

# Page Created: /<path>

## Files Created
- Page: app/<path>/page.tsx (or pages/<path>.tsx)
- Loading: app/<path>/loading.tsx (if App Router)
- Error: app/<path>/error.tsx (if App Router)

## Rendering Strategy
- Method: [SSG/SSR/ISR]
- Rationale: [Why this strategy was chosen]

## Usage

### Navigation
\`\`\`typescript
import Link from 'next/link';
<Link href="/<path>">Go to page</Link>
\`\`\`

### Data Fetching
[Instructions based on rendering strategy]

## Next Steps
1. Implement data fetching logic
2. Add UI components
3. Configure metadata/SEO
4. Test on development server
5. Optimize performance

Read the full file on GitHub · 132 lines

Changes

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.

  1. 1mo ago First seen · 132 lines · 13 tokens per session scan A 04f9ac2e68f3

Subscribe to this mod's changes

create-page is a command published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 814 once invoked, about $0.0001 per session on Opus 5.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.