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/oculus-samples/unity-theworldbeyond/agents-mdgit clone --depth 1 https://github.com/oculus-samples/Unity-TheWorldBeyondWhat 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.00745 | $0.00745 |
| Opus 5 | $0.00373 | $0.00373 |
| Sonnet 5 | $0.00149 | $0.00149 |
| Haiku 4.5 | $0.00075 | $0.00075 |
Grade A, and why
Unity-TheWorldBeyond 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 2d 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions — The World Beyond
Unity mixed-reality showcase that demonstrates Scene API, Passthrough, Interaction SDK, Voice SDK, and Audio Spatializer features as a reference / template for MR projects on Meta Quest.
Source-of-truth files (read these first, do not duplicate their contents in this file)
For setup, build steps, SDK versions, and project layout, read:
README.md— official setup and instructionsProjectSettings/ProjectVersion.txt— Unity editor versionPackages/manifest.json— Unity package versions (MRUK, Meta XR Interaction SDK, Voice SDK, Audio Spatializer)Documentation/— per-feature deep dives (Scene API, Passthrough, Voice, Interaction, Audio Spatializer, Sample Scenes)LICENSE— license terms
Quest / Horizon-specific notes
- Scene API requires that Room Setup has already been run on the headset before connecting Quest Link; if you launch the editor while connected to a Quest with no captured room, the Scene data will be empty. Disconnect Link, run Room Setup on-device, then reconnect.
- macOS users cannot use Quest Link — build an APK and deploy to device instead.
- When Unity prompts to migrate hand tracking, keep
OVRHands(not the new XR Hands package); the sample is wired to OVRHands. - During APK build, choose "Yes (Ignore and continue)" when prompted about "Unsupported Input Handling".
- Git LFS is required (
git lfs installbefore cloning) per the README.
Meta Quest tooling
This is a Meta Quest / Horizon OS sample. The bespoke intro above is the source of truth for what this project is and how it's built — use it (and the files it points at) instead of restating facts from memory.
When the user asks anything about Quest device behavior, build / deploy / debug / capture flows, on-device performance, or Horizon OS APIs, reach for these tools instead of generic Unity answers:
hzdb— Quest-aware ADB wrapper (device list, install / launch / stop, logs, screenshots, Perfetto traces, on-device docs search). Already wired up as an MCP server via.mcp.json,.vscode/mcp.json, and.cursor/mcp.json. Also runnable directly:npx -y @meta-quest/hzdb <subcommand>.- Meta Quest Agentic Tools — the full skill set, including Unity-specific skills: https://github.com/meta-quest/agentic-tools. Install per your client (Claude Code:
/plugin install meta-vr@meta-quest; Gemini CLI:gemini extensions install https://github.com/meta-quest/agentic-tools; Cursor / VS Code: install the Meta Horizon extension from the Marketplace).
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.
- 2d ago First seen · 38 lines · 745 tokens per session scan A a14cf8b2eb66
Unity-TheWorldBeyond AGENTS.md is an instructions file published in the GitHub repository oculus-samples/Unity-TheWorldBeyond (369 stars, last pushed 3mo ago), licensed MIT. It adds 745 tokens to every session, about $0.0037 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
Unity-AI-Animation CLAUDE.md
Instructions for IvanMurzak/Unity-AI-Animation, covering claude.md, what this is, build / run, critical invariants and find detail in.
BuildersGate CLAUDE.md
Instructions for Thepizzapie/BuildersGate, covering setting up builders gate for a user, ask two things first, install, point it at a game and keys.
turn-based-game-mcp ui-components.instructions.md
React component development patterns for the turn-based games platform.
Unity-Phanto AGENTS.md
Instructions for oculus-samples/Unity-Phanto, covering agent instructions — project phanto, quest / horizon-specific notes and meta quest tooling.
unity-3d-to-sprite-baker copilot-instructions.md
Instructions for sinanata/unity-3d-to-sprite-baker: This repository follows the cross-tool AGENTS.md standard. Read /AGENTS.md for the full guide: the SpriteBaker API, the enqueue → cache → bind flow, the material rules, build and preview commands, and the pull-request checklist.
lore-weave AGENTS.md
AGENTS.md instructions for letuhao/lore-weave, covering agents.md — loreweave development guide, what this project is, architecture, services and key rules.