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-phanto/agents-mdgit clone --depth 1 https://github.com/oculus-samples/Unity-PhantoWhat 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.00792 | $0.00792 |
| Opus 5 | $0.00396 | $0.00396 |
| Sonnet 5 | $0.00158 | $0.00158 |
| Haiku 4.5 | $0.00079 | $0.00079 |
Grade A, and why
Unity-Phanto 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 yesterday.
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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions — Project Phanto
Unity Mixed Reality reference app for Meta Quest demonstrating Scene Mesh, Scene Model, Scene API objects, Depth API, and TruTouch haptics. Positioned as both a reference and a template for MR projects.
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, instructions, and the device compatibility tableProjectSettings/ProjectVersion.txt— Unity editor versionPackages/manifest.json— Unity package versions (Meta XR SDKs, Depth API, MR Utility Kit, Haptics)Documentation/MainScenes.md,Documentation/ExampleScenes.md— which scenes to loadDocumentation/KeyComponents.md,DesignFlow.md,HealthAndSafetyGuidelines.md— system docsLICENSE.txt— license terms
Quest / Horizon-specific notes
- Git LFS is required. Run
git lfs installbefore cloning. Scene Data Sourceis a runtime switch inSceneDataLoaderSettings.asset:Scene Apifor headset / Quest Link,Static Mesh Datafor desk-bound dev with no live scene model. If scene mesh looks "missing", check that toggle first.- Scene Mesh is Quest 3 only. Color passthrough works on Quest 3 / Quest Pro. Quest 2 supports Scene API only. The compatibility table in
README.mdis authoritative — don't debug missing capabilities on unsupported devices. - Room scans must be triggered on the headset itself, even when running via Quest Link from the editor.
- Haptic clips were authored in Haptics Studio; replacing them with synthesized vibration is a fidelity regression.
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:
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.
- yesterday First seen · 39 lines · 792 tokens per session scan A 3b770ad79802
Unity-Phanto AGENTS.md is an instructions file published in the GitHub repository oculus-samples/Unity-Phanto (272 stars, last pushed 3mo ago), licensed MIT. It adds 792 tokens to every session, about $0.0040 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-TheWorldBeyond copilot-instructions.md
Instructions for oculus-samples/Unity-TheWorldBeyond: This is a Meta Quest / Horizon OS sample.
Unity-TheWorldBeyond GEMINI.md
Instructions for oculus-samples/Unity-TheWorldBeyond, a project described as: Presence Platform showcase demonstrating usage of Scene, Passthrough, Interaction, Voice, and Spatializer. The Oculus SDK and other supporting material is subject to the Oculus proprietary license. Multiple licenses may apply.
Unity-TheWorldBeyond AGENTS.md
Instructions for oculus-samples/Unity-TheWorldBeyond, covering agent instructions — the world beyond, quest / horizon-specific notes and meta quest tooling.
Unity-TheWorldBeyond meta-quest.instructions.md
Instructions for oculus-samples/Unity-TheWorldBeyond: For this repository, prefer Meta Quest Agentic Tools, the Meta Horizon VS Code/Cursor extension, and the hzdb MCP server.
Claw3D AGENTS.md
Instructions for iamlukethedev/Claw3D, covering agent instructions, cursor cloud specific instructions, service overview, running the app and lint, typecheck, and tests.
GameDesignOS AGENTS.md
Instructions for DY-2026/GameDesignOS, covering gamedesignos agent 入口, 默认接法, agent 执行规则, 什么时候用整个项目 and 每个 skill 单独怎么用.