Next-js-Boilerplate: Instructions file for Codex

AGENTS.md

Next-js-Boilerplate AGENTS.md is an instructions file for Codex, OpenCode from ixartz/Next-js-Boilerplate. It costs 881 tokens per session, scanned A, original, MIT.

A project-specific set of instructions for working on the ixartz/Next-js-Boilerplate repository. Next.js is a framework for building web applications with JavaScript or TypeScript.

In plain words
What is it for?
Use it when editing this repository, checking types or dependencies, linting, running tests, building locally, checking translations, or following its commit conventions.
Why use it?
It tells coding agents which code patterns, commands, and conventions this repository expects. That reduces accidental style changes and incorrect maintenance steps.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is ixartz/Next-js-Boilerplate's own configuration. It tells Codex and OpenCode how to work on Next-js-Boilerplate itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Next-js-Boilerplate configures →

About the project

Next-js-Boilerplate is a ready-made starting project for building Next.js applications with TypeScript, Tailwind CSS, routing, authentication, databases, testing, and development tools. Developers use it to create new web applications without assembling the foundation from scratch. Its catalogue instructions guide coding agents working in this starter project.

ixartz/Next-js-Boilerplate · 13,092 stars · on GitHub · nextjs-boilerplate.com

Reuse

Borrowing it

Nothing to install: this file belongs to ixartz/Next-js-Boilerplate. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ixartz/Next-js-Boilerplate/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/ixartz/Next-js-Boilerplate

Made for: Codex, OpenCode.

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 Next-js-Boilerplate AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/ixartz/next-js-boilerplate/agents-md/github.svg)](https://agentmods.dev/instructions/ixartz/next-js-boilerplate/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/ixartz/next-js-boilerplate/agents-md"><img src="https://agentmods.dev/badge/instructions/ixartz/next-js-boilerplate/agents-md/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 Next-js-Boilerplate AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/ixartz/next-js-boilerplate/agents-md"><img src="https://agentmods.dev/badge/instructions/ixartz/next-js-boilerplate/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 881 This file is loaded in full into every session.
When invoked 881 The same file — it is already loaded in full.
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.00881 $0.00881
Opus 5.5 $0.00352 $0.00352
Sonnet 5.5 $0.00176 $0.00176
Haiku 4.5 $0.00088 $0.00088

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

Security

Grade A, and why

Next-js-Boilerplate AGENTS.md 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 2mo 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.

AGENTS.md · 68 lines

How it starts

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

AGENTS

Principles

  • Clarity and consistency over cleverness. Minimal changes. Match existing patterns.
  • Keep components/functions short; break down when it improves structure.
  • TypeScript everywhere; no any unless isolated and necessary.
  • No unnecessary try/catch. Avoid casting; use narrowing.
  • Named exports only (no default exports, except Next.js pages).
  • Absolute imports via @/ unless same directory.
  • Follow existing ESLint setup; don't reformat unrelated code.
  • Zod type-only: import type * as z from 'zod';.
  • Let compiler infer return types unless annotation adds clarity.
  • Options object for 3+ params, optional flags, or ambiguous args.
  • Hypothesis-driven debugging: 1-3 causes, validate most likely first.

Token efficiency

  • Skip recaps unless the result is ambiguous or you need more input.

Commands

Only these bun run scripts: build-local, lint, check:types, check:deps, check:i18n, test, test:e2e.

Git Commits

Conventional Commits: type: summary without scope. The summary should be a short, specific sentence that explains what changed and where or why, not a vague phrase. Types: feat|fix|docs|style|refactor|perf|test|build|ci|chore|revert. BREAKING CHANGE: footer when needed.

Env

All env vars validated in Env.ts; never read process.env directly.

Styling

Tailwind v4 utility classes. Reuse shared components. Responsive. No unnecessary classes.

React

  • No useMemo/useCallback (React compiler handles it). Avoid useEffect.
  • Single props param with inline type; access as props.foo (no destructuring).
  • Use React.ReactNode, not ReactNode.
  • Inline short event handlers; extract only when complex.

Pages

  • Default export name ends with Page. Props alias (if reused) ends with PageProps.
  • Locale pages: props: { params: Promise<{ locale: string }> } → await props.params → setRequestLocale(locale).
  • Escape glob chars in shell commands for Next.js paths.
  • Dashboard pages (sit behind auth); define meta once in layout, not in each page.

Read the full file on GitHub · 68 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. 2mo ago First seen · 68 lines · 881 tokens per session scan A 944926e3fc7a

Subscribe to this mod's changes

Next-js-Boilerplate AGENTS.md is an instructions file published in the GitHub repository ixartz/Next-js-Boilerplate (13,092 stars, last pushed 21d ago), licensed MIT. It adds 881 tokens to every session, about $0.0035 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.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens