agentmods.dev

build-app-page

build-app-page is a skill for Claude Code, Codex from internet-development/nextjs-css-agent-components. It costs 107 tokens per session (3,962 once invoked), scanned A, original, MIT.

A workflow for creating a new page in a Next.js application using the repository's existing components and layout patterns. Next.js is a framework for building web applications, and this setup uses its Pages Router for page URLs.

In plain words
What is it for?
Building dashboards, settings screens, document pages, forms, galleries, marketing pages, and other new routes under the repository's pages directory.
Why use it?
It helps a new page fit the application's existing design, imports, layout, and metadata conventions. It also checks that the page can start and render correctly.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions AGENTS.md.

not rated 217repo 2mo ago A scan SkillSpector: pass 107 tokens original MIT

Good fit Building dashboards, settings screens, document pages, forms, galleries, marketing pages, and other new routes under the repository's pages directory.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/internet-development/nextjs-css-agent-components/build-app-page
View source ↗ internet-development/nextjs-css-agent-components wireframes.internet.dev
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.

Any agent
npx skills add internet-development/nextjs-css-agent-components --skill build-app-page
Clone the repo
git clone --depth 1 https://github.com/internet-development/nextjs-css-agent-components

Made for: Claude Code, Codex.

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 build-app-page

README.md
[![agentmods](https://agentmods.dev/badge/skills/internet-development/nextjs-css-agent-components/build-app-page/github.svg)](https://agentmods.dev/skills/internet-development/nextjs-css-agent-components/build-app-page)
Your own site
<a href="https://agentmods.dev/skills/internet-development/nextjs-css-agent-components/build-app-page"><img src="https://agentmods.dev/badge/skills/internet-development/nextjs-css-agent-components/build-app-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 build-app-page

Your own site · 80×15
<a href="https://agentmods.dev/skills/internet-development/nextjs-css-agent-components/build-app-page"><img src="https://agentmods.dev/badge/skills/internet-development/nextjs-css-agent-components/build-app-page.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 107 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,962 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00107 $0.03962
Opus 5.5 $0.00043 $0.01585
Sonnet 5.5 $0.00021 $0.00792
Haiku 4.5 $0.00011 $0.00396

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

Security

Grade A, and why

build-app-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.

public/skills/build-app-page/SKILL.md · 390 lines

How it starts

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

Build an app page

This skill walks an empty .tsx file to a working app page that uses this repo's three-tier system correctly. The end state: a page that boots in npm run dev, renders with the right chrome and layout, has the right SEO metadata, and follows the import-tier rules from AGENTS.md.

When to use

  • "Build a settings page for X"
  • "Create a new dashboard for Y"
  • "Add a documents page for Z"
  • "Scaffold a new authenticated app screen"
  • "Make a marketing landing page using our components"
  • Any time the user wants a new route under pages/ that uses the design system

When NOT to use

  • The user just wants to modify an existing page (use direct edits).
  • The user wants a non-page React component (use the component conventions in AGENTS.md instead).
  • The user wants App Router (app/) page work — this repo's routes live under Pages Router (pages/). Stop and ask before introducing App Router.

Pre-flight: pin down what you're building

Before writing anything, ask yourself (or the user) four questions:

  1. What's the page's purpose? Marketing/landing, authenticated app screen, document viewer, dashboard, form, or gallery showcase? Each has a canonical layout pattern below.
  2. Does it need a session/API key? If yes, use KeyHeader and the getServerSideProps → Server.setup(context) pattern (see "Authenticated app pages" below). If no, plain Navigation + getServerSideProps returning { props: {} } is enough.
  3. Does it open modals? If yes, you must render <GlobalModalManager /> and import useModals from @runtime/modals/ModalContext.
  4. Is it a gallery showcase? If yes, you'll register it in common/constants.ts after writing.

Pick the page shape

Match the page to one of these canonical shapes. Each is taken straight from a working file in pages/examples/.

Shape A — Marketing / showcase page (Navigation + content + Footer)

Use when: landing pages, "show off this component" pages, content pages.

Read the full file on GitHub · 390 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 · 390 lines · 107 tokens per session scan A 8084f684d941

Subscribe to this mod's changes

build-app-page is a skill published in the GitHub repository internet-development/nextjs-css-agent-components (217 stars, last pushed 2mo ago), licensed MIT. It adds 107 tokens to every session and 3,962 once invoked, about $0.0004 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-08-30.

Frontendagent-uinextjstemplatewebsite-template
Related

Other skills, from other repositories

portaljs-new-portal

Scaffold a new PortalJS data portal from a brief. Copies the canonical template from examples/portaljs-catalog and substitutes project tokens. Use when starting a brand-new data portal project from scratch.

datopian/portaljs · 46 tokens

ultracite

Ultracite is a zero-config linting and formatting preset for JavaScript/TypeScript projects. Use when: (1) Setting up or initializing Ultracite in a project (ultracite init), (2) Running linting or formatting commands (check, fix, doctor), (3) Writing or reviewing JS/TS code in a project that uses Ultracite — to…

agustinusnathaniel/nextarter-tailwind · 142 tokens

next-upgrade

Upgrade Next.js to the latest version following official migration guides and codemods.

agustinusnathaniel/nextarter-tailwind · 19 tokens

vercel-composition-patterns

React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.

agustinusnathaniel/nextarter-tailwind · 58 tokens

vercel-react-best-practices

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance…

agustinusnathaniel/nextarter-tailwind · 67 tokens

vercel-react-view-transitions

Guide for implementing smooth, native-feeling animations using React's View Transition API ( component, addTransitionType, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components…

agustinusnathaniel/nextarter-tailwind · 127 tokens