Borrowing it
Nothing to install: this file belongs to Kazuki-tam/next-stage. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Kazuki-tam/next-stage/main/AGENTS.mdgit clone --depth 1 https://github.com/Kazuki-tam/next-stageWrote 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.
[](https://agentmods.dev/instructions/kazuki-tam/next-stage/agents-md)<a href="https://agentmods.dev/instructions/kazuki-tam/next-stage/agents-md"><img src="https://agentmods.dev/badge/instructions/kazuki-tam/next-stage/agents-md.svg" alt="Measured on agentmods" height="20"></a>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.02789 | $0.02789 |
| Opus 5 | $0.01394 | $0.01394 |
| Sonnet 5 | $0.00558 | $0.00558 |
| Haiku 4.5 | $0.00279 | $0.00279 |
Grade A, and why
next-stage 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 370 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Project Overview
Key Technologies:
- Framework: Next.js 16.3.0 with App Router
- Runtime: React 19.2.8, React DOM 19.2.8
- Language: TypeScript 5.9.3
- Package Manager: Bun 1.3.14
- API Framework: Hono 4.13.0
- API Validation: @hono/zod-validator 0.7.6
- UI Components: shadcn/ui with Radix UI
- Styling: Tailwind CSS 4.3.3
- Form Management: React Hook Form 7.84.0 + Zod 4.4.3
- Icons: lucide-react 1.28.0
- Testing: Playwright 1.61.1 + Bun test runner
- Code Quality: Biome 2.3.8 + Markuplint 4.18.3
Setup Commands
# Install dependencies
bun install
# Start development server (Turbopack is default in Next.js 16)
bun dev
# Build for production
bun build
# Start production server
bun start
# Run all tests
bun run test:unit && bun run test:e2e
# Run code quality checks (linting + formatting)
bun run check
Development Environment
Package Manager
- Primary: Use
bunfor all package management and script execution - Performance: Turbopack is the default bundler in Next.js 16 for faster development builds
- Hot Reload: Development server runs on http://localhost:3000 with auto-refresh
Directory Structure
Follow the established colocation pattern:
src/
├── app/ # Next.js App Router routes
│ ├── _components/ # App-specific components
│ ├── _styles/ # App-specific styles
│ └── page.tsx # Route pages
├── components/ # Reusable UI components
│ ├── layout/ # Layout-specific components
│ └── ui/ # shadcn/ui components
├── config/ # Configuration files
├── lib/ # Utility functions and shared logic
└── types/ # Shared type definitions
File Naming Conventions
- Use lowercase with dashes for directories:
auth-user/,user-profile/ - Use underscore prefix for page-specific directories:
_components/,_actions/,_hooks/ - Component files: PascalCase with
.tsxextension - Utility files: camelCase with
.tsextension
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.
- 8d ago First seen · 370 lines · 2,789 tokens per session scan A d2c5b3618eea
next-stage AGENTS.md is an instructions file published in the GitHub repository Kazuki-tam/next-stage (12 stars, last pushed 1mo ago), licensed MIT. It adds 2,789 tokens to every session, about $0.0139 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-30.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
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.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.