audit

A command that scans a Next.js project for common problems in routing, components, performance, and configuration. Next.js is a framework for building web applications with JavaScript or TypeScript.

In plain words
What is it for?
Use `/audit` to inspect routing, component structure, performance, or all supported areas of a Next.js project.
Why use it?
It helps locate missing route boundaries, incorrect server/client component use, oversized bundles, and other setup issues.

Command

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.

agentmods
npx agentmods add commands/iwritec0de/app-dev/audit
Clone the repo
git clone --depth 1 https://github.com/iwritec0de/app-dev
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 978 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00017 $0.00978
Opus 5 $0.00009 $0.00489
Sonnet 5 $0.00003 $0.00196
Haiku 4.5 $0.00002 $0.00098

Measured yesterday against content hash 7404dfcc9e6d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

audit 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 yesterday.

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.

commands/audit.md · 114 lines

How it starts

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

Next.js Audit

Scan a Next.js project for common issues, anti-patterns, and misconfigurations.

Load the nextjs-expert skill for App Router patterns and security best practices.

Usage

/audit [--focus routing|components|performance|all]

Arguments

Parse $ARGUMENTS to extract:

  • --focus (optional, default: all)
    • routing — Route structure, missing error/loading boundaries, middleware issues
    • components — Client/server component misuse, missing use client, prop drilling
    • performance — Bundle size, unoptimized images, unnecessary client-side JS
    • all — Run everything

Instructions

1. Detect Next.js Version & Router

cat package.json | grep -E '"next"'
ls app/ 2>/dev/null && echo "App Router"
ls pages/ 2>/dev/null && echo "Pages Router"
ls next.config.* 2>/dev/null

2. Routing Audit

App Router:

  • Search for missing error.tsx boundaries in route segments
  • Search for missing loading.tsx where data fetching occurs
  • Check for missing not-found.tsx at the root
  • Verify layout.tsx exists at the root
  • Check for route groups (group) organization
  • Look for parallel routes and intercepting routes usage
  • Verify generateStaticParams is used for dynamic routes that could be static
  • Check middleware.ts for correctness (matcher patterns, edge runtime compatibility)

Pages Router:

  • Check for _app.tsx, _document.tsx, _error.tsx
  • Look for getStaticProps vs getServerSideProps usage (prefer static when possible)
  • Check for missing getStaticPaths on dynamic routes

3. Component Audit

Search for:

  • Missing 'use client' — Components using hooks (useState, useEffect, useRef) without the directive
  • Unnecessary 'use client' — Components marked client that don't need to be (no hooks, no browser APIs)
  • Server component data fetchingfetch() calls in server components without proper caching directives
  • Large client components — Components with 'use client' that import heavy libraries (could split)
  • Prop drilling — Deep prop passing that should use server components or context
  • Missing Suspense boundaries — Async server components without Suspense wrappers
  • Direct DOM manipulationdocument. or window. without proper guards

Read the full file on GitHub · 114 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. yesterday First seen · 114 lines · 17 tokens per session scan A 7404dfcc9e6d

Subscribe to this mod's changes

audit is a command published in the GitHub repository iwritec0de/app-dev (3 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 978 once invoked, about $0.0001 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.