What is vite-flare-starter AGENTS.md?

Project instructions for a React and Vite starter application running on Cloudflare Workers, with predefined modules for web pages, data, authentication, and AI features.

Use them when adding or changing modules, controlling optional features, running tests, generating database migrations, or deploying this specific project.

They tell coding agents which files and commands are authoritative, how to follow existing modules, and how to test, type-check, build, and deploy the project.

How jezweb/vite-flare-starter configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to jezweb/vite-flare-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/jezweb/vite-flare-starter/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/jezweb/vite-flare-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/jezweb/vite-flare-starter/agents-md/github.svg)](https://agentmods.dev/instructions/jezweb/vite-flare-starter/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/jezweb/vite-flare-starter/agents-md"><img src="https://agentmods.dev/badge/instructions/jezweb/vite-flare-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/jezweb/vite-flare-starter/agents-md"><img src="https://agentmods.dev/badge/instructions/jezweb/vite-flare-starter/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 657 This file is loaded in full into every session.

When invoked 657 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.00657	$0.00657
Opus 5.5	$0.00263	$0.00263
Sonnet 5.5	$0.00131	$0.00131
Haiku 4.5	$0.00066	$0.00066

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

Security

Grade A, and why

vite-flare-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 · 54 lines

How it starts

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

Vite Flare Starter — agent guide

Pattern library + production starter for Cloudflare Workers apps. React 19 + Vite, Hono, D1 (Drizzle), R2, better-auth, AI SDK v6 with the Cloudflare agents SDK. Modules are reference implementations — read the closest existing module before building a new one, and disable unwanted modules with VITE_FEATURE_* flags instead of deleting them.

This file is deliberately compact. CLAUDE.md is the canonical deep context (module map, AI stack, auth model) and stays current — read it next. This file only carries what every coding agent needs on turn one.

Commands

pnpm dev                    # dev server (Docker must run — sandbox container builds)
pnpm build                  # production build
pnpm run deploy             # build + deploy (NEVER bare `wrangler deploy` — stale dist)
pnpm test                   # unit tests (Vitest, Workers pool)
pnpm test:e2e               # Playwright killer flows (against live deploy)
pnpm type-check             # tsc --noEmit
pnpm db:generate:named "x"  # create migration
pnpm db:migrate:local       # apply migrations locally
pnpm db:migrate:remote      # apply migrations to production
pnpm doctor:auth            # diagnose better-auth setup issues
pnpm doctor:models          # check Workers AI model ids against live catalogue

Conventions that bite if missed

Design tokens only — semantic classes (bg-background, border-hairline), never raw palette classes or .dark {} overrides. See DESIGN.md.
Tenancy: scope reads AND write-guards with scopeUser() (src/server/lib/tenancy.ts); polymorphic lookups go through canAccessEntity(). R2 keys gate on isOwnedR2Key().
New agent tools follow the one-file ToolDefinition contract (.claude/rules/one-file-tool-definitions.md) — server execute + client render metadata in one object.
New DO/agent classes must declare an AGENT_ACCESS_POLICY entry in src/server/index.ts (fail-closed) and be exported for wrangler.
shadcn components are Base UI (render prop, not asChild); icons are Phosphor; charts are Kumo ECharts.

Read the full file on GitHub · 54 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 · 54 lines · 657 tokens per session scan A 3c6c17c88483

Subscribe to this mod's changes

vite-flare-starter AGENTS.md is an instructions file published in the GitHub repository jezweb/vite-flare-starter (49 stars, last pushed 22d ago), licensed MIT. It adds 657 tokens to every session, about $0.0026 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.

Cloud DevOps and cloud Frontend React

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

vite-flare-starter: Instructions file for Codex

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Vite Flare Starter — agent guide

Commands

Conventions that bite if missed

What this file has done since we first saw it

Other instructions, from other repositories

vscode buildNext.instructions.md

next.js AGENTS.md

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

langchain AGENTS.md

vscode copilot-instructions.md

vscode model-prompts.instructions.md