What is nextjs-loop-engineering-starter AGENTS.md?

Project instructions for a Next.js task-management application built with TypeScript, SQLite, and automated tests. They explain the codebase, its development loop, and the commands agents should use.

Use them when starting a development loop, understanding the project stack, resetting the database, running end-to-end tests, or running the full verification pipeline.

They give coding agents the project context and verification rules needed to make changes that fit the existing application. They also identify the required checks before work is considered complete.

How muzafferkadir/nextjs-loop-engineering-starter configures Codex and

Reuse

Borrowing it

Nothing to install: this file belongs to muzafferkadir/nextjs-loop-engineering-starter. 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/muzafferkadir/nextjs-loop-engineering-starter/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/muzafferkadir/nextjs-loop-engineering-starter

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/muzafferkadir/nextjs-loop-engineering-starter/agents-md/github.svg)](https://agentmods.dev/instructions/muzafferkadir/nextjs-loop-engineering-starter/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/muzafferkadir/nextjs-loop-engineering-starter/agents-md"><img src="https://agentmods.dev/badge/instructions/muzafferkadir/nextjs-loop-engineering-starter/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/muzafferkadir/nextjs-loop-engineering-starter/agents-md"><img src="https://agentmods.dev/badge/instructions/muzafferkadir/nextjs-loop-engineering-starter/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,479 This file is loaded in full into every session.

When invoked 1,479 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.

Model	Per session	Once invoked
Fable 5.1	$0.01479	$0.01479
Opus 5.5	$0.00592	$0.00592
Sonnet 5.5	$0.00296	$0.00296
Haiku 4.5	$0.00148	$0.00148

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

Security

Grade A, and why

nextjs-loop-engineering-starter 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 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.

AGENTS.md · 134 lines

How it starts

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

AGENTS.md — Project Instructions for AI Agents

How to Start a Loop

See README.md → "Developing with the Loop" for the Report/Build mode commands. Skills live in .claude/skills/<name>/SKILL.md.

Project Purpose

A task management web application built with Next.js and developed through loop engineering. Treat this as a real product codebase: the backlog in BACKLOG.md defines what to build next, and every change goes through the verifier pipeline. Whatever the product owner puts in BACKLOG.md is the product — build that.

Stack

Next.js 15 (App Router) · React 19 · TypeScript (strict)
Tailwind CSS 4 + shadcn/ui conventions (components.json is configured)
SQLite + Drizzle ORM (zero external services)
Vitest (unit) · Playwright (e2e, deterministic config)

Commands

pnpm db:reset         # push schema + deterministic seed — run once after clone
pnpm e2e              # Playwright e2e (starts its own server, reseeds DB)
pnpm verify           # THE verification pipeline — same as CI
pnpm snap [routes]    # screenshot pages for visual inspection (dev server must run)

Code Rules

TypeScript

strict: true and noUncheckedIndexedAccess: true — never use any (the verifier rejects diffs containing any)
Validate every external input (form data, search params) with Zod

Next.js

Server Components by default — add "use client" only where the component needs state, effects, or event handlers
Mutations go through Server Actions in actions.ts files colocated with the route (see src/app/tasks/actions.ts for the reference pattern: auth check → Zod parse → ownership check → mutate → revalidatePath)
Every route with async data gets loading.tsx and error.tsx (see src/app/tasks/ for the reference implementation)
Auth: call getCurrentUser() from @/lib/auth in server code. Never edit src/lib/auth.ts — it is denylisted.

Database (Drizzle + SQLite)

Schema: src/db/schema.ts. Always query through db from @/db/client
Schema change flow: edit schema → pnpm db:push locally → note in the PR that a migration is needed. Schema changes always need human review
Deletes are soft (deletedAt) — follow the pattern in tasks
Never edit src/db/seed.ts randomness rules: seeds stay deterministic (fixed IDs, fixed dates), e2e depends on it

Read the full file on GitHub · 134 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.

1mo ago First seen · 134 lines · 1,479 tokens per session scan A 99dc535789a3

Subscribe to this mod's changes

nextjs-loop-engineering-starter AGENTS.md is an instructions file published in the GitHub repository muzafferkadir/nextjs-loop-engineering-starter (10 stars, last pushed 3mo ago), licensed MIT. It adds 1,479 tokens to every session, about $0.0059 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-31.

Claude Code agentic-coding ai-agents ai-coding-agent codex loop-engineering

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

nextjs-loop-engineering-starter: Instructions file for Codex