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.
npx agentmods add instructions/cloudflare/vinext/agents-mdgit clone --depth 1 https://github.com/cloudflare/vinextWhat 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 | $0.08517 | $0.08517 |
| Opus 5 | $0.04258 | $0.04258 |
| Sonnet 5 | $0.01703 | $0.01703 |
| Haiku 4.5 | $0.00852 | $0.00852 |
Grade A, and why
vinext 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 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.
How it starts
The opening of the file, as written. The whole thing — 560 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Guidelines
Instructions for AI agents working on this codebase.
Project Overview
vinext is a Vite plugin that reimplements the Next.js API surface, with Cloudflare Workers as the primary deployment target. The goal: take any Next.js app and deploy it to Workers with one command.
vinext reimplements the Next.js API surface using Vite, with Cloudflare Workers as the primary deployment target. The goal is to let developers keep their existing Next.js code and deploy it to Workers.
Quick Reference
Commands
pnpm test # Vitest — full suite (~2 min, serial)
pnpm test tests/routing.test.ts # Run a single test file (~seconds)
pnpm test tests/shims.test.ts tests/link.test.ts # Run specific files
pnpm run test:e2e # Playwright E2E tests (all projects, use PLAYWRIGHT_PROJECT=<name> to target one)
pnpm run check # Format, lint, and type checks
pnpm run lint # Lint only (type-aware oxlint)
pnpm run fmt # oxfmt (format)
pnpm run fmt:check # oxfmt (check only, no writes)
pnpm run build # Build the vinext package (via vp pack)
Project Structure
packages/vinext/src/
index.ts # Main Vite plugin
cli.ts # vinext CLI
shims/ # One file per next/* module
routing/ # File-system route scanners
server/ # SSR handlers, ISR, middleware
cloudflare/ # KV cache handler
tests/
*.test.ts # Vitest tests
fixtures/ # Test apps (pages-basic, app-basic, etc.)
e2e/ # Playwright tests
examples/ # User-facing demo apps
Key Files
| File | Purpose |
|---|---|
index.ts |
Vite plugin — resolves next/* imports, generates virtual modules |
shims/*.ts |
Reimplementations of next/link, next/navigation, etc. |
server/dev-server.ts |
Pages Router SSR handler |
entries/app-rsc-entry.ts |
App Router RSC entry generator |
routing/pages-router.ts |
Scans pages/ directory |
routing/app-router.ts |
Scans app/ directory |
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.
- yesterday First seen · 560 lines · 8,517 tokens per session scan A eb0be11046e2
vinext AGENTS.md is an instructions file published in the GitHub repository cloudflare/vinext (8,698 stars, last pushed 3d ago), licensed MIT. It adds 8,517 tokens to every session, about $0.0426 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.
buildNext
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
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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
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.
langchain 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.