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/meta-quest/webxr-first-steps/agents-mdgit clone --depth 1 https://github.com/meta-quest/webxr-first-stepsWrote 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/meta-quest/webxr-first-steps/agents-md)<a href="https://agentmods.dev/instructions/meta-quest/webxr-first-steps/agents-md"><img src="https://agentmods.dev/badge/instructions/meta-quest/webxr-first-steps/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.01240 | $0.01240 |
| Opus 5 | $0.00620 | $0.00620 |
| Sonnet 5 | $0.00248 | $0.00248 |
| Haiku 4.5 | $0.00124 | $0.00124 |
Grade A, and why
webxr-first-steps 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 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.
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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions — WebXR First Steps
This repository is WebXR First Steps, a 2-hour tutorial project that walks web developers through building their first immersive WebXR experience using Three.js. By the end of the tutorial the user has a target-practice VR game with controller input, sound, vibration, and animations.
Stack and key facts
- Platform: WebXR in the browser (Meta Quest Browser, desktop Chrome with WebXR emulation, etc.).
- Engine: Three.js
0.165.0with@types/three 0.165.0. - Bundler / dev server: Webpack 5.94 +
webpack-dev-server 5.1, served athttps://localhost:8081. - Runtime deps:
three,gamepad-wrapper 1.3.4,gsap 3.12.5,troika-three-text 0.49.1,iwer 1.0.4,@iwer/devui 0.1.1. - Toolchain: Node.js
20.x+ and npm10.x+. - License: MIT (
LICENSE). - Project layout:
src/—index.html,index.js,init.js, andassets/(init.js wires the IWER emulator when native WebXR is missing).tutorial/— chapter markdown (chapter1.mdthroughchapter6.md) plusassets/.webpack.config.cjs,eslint.config.cjs,prettier.config.cjs— build/format config.
- Git LFS: not required.
Build and run
git clone https://github.com/meta-quest/webxr-first-steps.git && cd webxr-first-steps.- Confirm Node.js
20.x+ and npm10.x+ are installed (node -v,npm -v). npm install.npm run dev— startswebpack serveathttps://localhost:8081.- Open in a WebXR-capable browser, either:
- On the Quest headset directly, by IP (e.g.
https://192.168.0.123:8081/) — dismiss the self-signed cert warning. - Via
chrome://inspect/#devicesADB port forwarding tolocalhost:8081. - On desktop with the built-in IWER emulator (auto-activates when no native WebXR runtime is present).
- On the Quest headset directly, by IP (e.g.
Production build: npm run build.
What the sample demonstrates
A staged tutorial in tutorial/chapter1.md through chapter6.md covering scene setup, VR controllers, gameplay (target shooting + score), audio, haptic vibration, and animation. The completed game is Target Practice (see tutorial/assets/targetpractice.gif).
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 · 93 lines · 1,240 tokens per session scan A f7871b0bbd85
webxr-first-steps AGENTS.md is an instructions file published in the GitHub repository meta-quest/webxr-first-steps (177 stars, last pushed 3mo ago), licensed MIT. It adds 1,240 tokens to every session, about $0.0062 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
adsb-3d CLAUDE.md
Instructions for hook-365/adsb-3d, covering claude.md, what this is, repo layout, frontend architecture and adding a setting.
realvirtual-WEB CLAUDE.md
Claude Code instructions for game4automation/realvirtual-WEB, covering claude.md — realvirtual web, project overview, quick start, code conventions and file naming.
hana-developer-cli-tool-example command-documentation.instructions.md
Use when creating or updating CLI command documentation in docs/02-commands/. Generates comprehensive markdown files with Mermaid diagrams showing command flow, detailed parameter tables organized by category, syntax examples, and related commands.
hana-developer-cli-tool-example cli-command-development.instructions.md
Use when creating or updating CLI command files in bin/. Enforces consistent structure, imports, exports, error handling, internationalization, and integration with the command infrastructure. Ensures commands work seamlessly with the yargs framework, prompt system, and database connections.
hana-developer-cli-tool-example mcp-server-development.instructions.md
Use when creating or updating MCP (Model Context Protocol) server components. Enforces TypeScript patterns, JSON-RPC communication rules, tool/resource/prompt registration, and integration with CLI command metadata. Ensures MCP server follows protocol requirements and maintains consistency with the CLI infrastructure.
hana-developer-cli-tool-example route-development.instructions.md
Use when creating or updating route files in routes/. Enforces consistent structure, error handling, database connection management, internationalization, and integration with the Express server and CLI command infrastructure. Ensures routes follow established patterns for endpoint registration, response formatting…