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/pi0/vite-plugin-remix3/agents-mdgit clone --depth 1 https://github.com/pi0/vite-plugin-remix3Wrote 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/pi0/vite-plugin-remix3/agents-md)<a href="https://agentmods.dev/instructions/pi0/vite-plugin-remix3/agents-md"><img src="https://agentmods.dev/badge/instructions/pi0/vite-plugin-remix3/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 | $0.02362 | $0.02362 |
| Opus 5 | $0.01181 | $0.01181 |
| Sonnet 5 | $0.00472 | $0.00472 |
| Haiku 4.5 | $0.00236 | $0.00236 |
Grade A, and why
vite-plugin-remix3 AGENTS.md scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Workaround: register an `ssr` env (default input `app/router.ts`) so the rendering chain builds in the pre-manifest loop. Nitro auto-wires the renderer to `ssrRenderer` (from `runtime/internal/vite/ssr-renderer.mjs`), wh How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vite-plugin-remix3
vite-plugin-remix3 lets a Remix v3 app build through Vite + Nitro: client entries are bundled and hashed, SSR resolves URLs through Vite's manifest, and Nitro handles deployment. The plugin replaces what createAssetServer would do compile on demand in runtime.
Keep AGENTS.md updated with critical information about project.
Repo layout
| Path | Purpose |
|---|---|
| src/index.ts | The plugin. Discovers client entries, registers client + ssr Vite environments. |
| build.config.ts | obuild config — bundles src/index.ts to dist/index.mjs. |
| package.json | Publishes dist/. Peer-deps vite ^8. Built via pnpm build. |
| pnpm-workspace.yaml | Workspace root. Includes ./starter. Overrides vite-plugin-remix3 to workspace:*. |
| starter/ | Example app consumed by pnpm dev / pnpm dev:build. Wired through the workspace override. |
| starter/vite.config.ts | plugins: [nitro(), remix()]. No server.ts — Nitro auto-routes through the SSR env. |
| starter/app/router.ts | Route → controller mapping. Exports router. No default export. |
| starter/app/entry.server.ts | SSR entry (default ssrEntry). export default { fetch: router.fetch } — Nitro's fetch handler. |
| starter/app/entry.client.ts | Client bootstrap. import.meta.glob map + run({ loadModule, resolveFrame }) from remix/ui. |
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.
- 4d ago First seen · 107 lines · 2,362 tokens per session scan A b6b87e706ed2
vite-plugin-remix3 AGENTS.md is an instructions file published in the GitHub repository pi0/vite-plugin-remix3 (23 stars, last pushed 3mo ago), licensed MIT. It adds 2,362 tokens to every session, about $0.0118 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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).
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.
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.
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).
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.