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/orval-labs/orval/agents-mdgit clone --depth 1 https://github.com/orval-labs/orvalWrote 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/orval-labs/orval/agents-md)<a href="https://agentmods.dev/instructions/orval-labs/orval/agents-md"><img src="https://agentmods.dev/badge/instructions/orval-labs/orval/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.00439 | $0.00439 |
| Opus 5 | $0.00219 | $0.00219 |
| Sonnet 5 | $0.00088 | $0.00088 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
orval 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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- terminus-mcp AGENTS.md — 88% identical, 7 lines differ
What it actually says
Using Vite+, the Unified Toolchain for the Web
This project is using Vite+, a unified toolchain built on top of Vite, Rolldown, Vitest, tsdown, Oxlint, Oxfmt, and Vite Task. Vite+ wraps runtime management, package management, and frontend tooling in a single global CLI called vp. Vite+ is distinct from Vite, and it invokes Vite through vp dev and vp build. Run vp help to print a list of commands and vp <command> --help for information about a specific command.
Docs are local at node_modules/vite-plus/docs or online at https://viteplus.dev/guide/.
Built-in Commands vs Scripts
vp <name> runs a built-in command. vp run <name> runs a package.json script or a vite.config.ts task. Scripts cannot overwrite built-ins, so vp dev and vp run dev may do different things. Check package.json and vite.config.ts first, and run vp run <name> when the project defines a script or task with that name.
Tool Versions
Run vp toolchain to show versions and relationships in the active Vite+
release. Add a tool name to select part of the graph. For example, run
vp toolchain vite. Use --global to ignore the local vite-plus package. Use
vp why <package> to show the package-manager dependency graph.
Review Checklist
- Run
vp installafter pulling remote changes and before getting started. - Run
vp checkandvp testto format, lint, type check and test changes. - Check if there are
vite.config.tstasks orpackage.jsonscripts necessary for validation, run viavp run <script>. - If setup, runtime, or package-manager behavior looks wrong, run
vp env doctorand include its output when asking for help.
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.
- 3d ago First seen · 28 lines · 439 tokens per session scan A 135ce87bb04f
orval AGENTS.md is an instructions file published in the GitHub repository orval-labs/orval (6,421 stars, last pushed today), licensed MIT. It adds 439 tokens to every session, about $0.0022 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-09-01.
Other instructions, from other repositories
core CLAUDE.md
Claude Code instructions for module-federation/core, covering claude task parallelization & development guidelines, core principles, maximum parallelization strategy, universal parallel task patterns and for any codebase task.
kubb AGENTS.md
AGENTS.md instructions for kubb-labs/kubb, covering agents.md, high-level architecture, project structure and commands, repository setup and plugin ecosystem.
ui-components AGENTS.md
AGENTS.md instructions for starc007/ui-components, covering beui v2 — agent guide, commands, layout, component catalog and components (motion category — primitives).
react-seed AGENTS.md
Instructions for guokaigdg/react-seed, covering agents.md, 目录, 1. 项目概览, 2. 技术栈 and 3. 目录结构.
walkerOS CLAUDE.md
Claude Code instructions for elbwalker/walkerOS, covering claude.md and important: use agent.md.
monochrome-ui AGENTS.md
AGENTS.md instructions for vaneenige/monochrome-ui, covering agents.md, north stars (non-negotiables), why the core looks weird (and should stay weird), clever tricks and code style.