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.
git clone --depth 1 https://github.com/meta-quest/Meta-Spatial-SDK-TemplatesWrote 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/commands/meta-quest/meta-spatial-sdk-templates/setup-meta-quest-tools)<a href="https://agentmods.dev/commands/meta-quest/meta-spatial-sdk-templates/setup-meta-quest-tools"><img src="https://agentmods.dev/badge/commands/meta-quest/meta-spatial-sdk-templates/setup-meta-quest-tools.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.1 | $0.00000 | $0.00056 |
| Opus 5 | $0.00000 | $0.00028 |
| Sonnet 5 | $0.00000 | $0.00011 |
| Haiku 4.5 | $0.00000 | $0.00006 |
Grade A, and why
setup-meta-quest-tools 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 7d 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.
This is a copy
100% identical to setup-meta-quest-tools — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Set up Meta Quest Agentic Tools
Run:
npx -y @meta-quest/hzdb mcp install open-code
Then inspect AGENTS.md and use the hzdb MCP server for Quest/Horizon OS tasks.
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.
- 7d ago First seen · 10 lines · 0 tokens per session scan A 654e88af35c9
setup-meta-quest-tools is a command published in the GitHub repository meta-quest/Meta-Spatial-SDK-Templates (4 stars, last pushed 1mo ago), licensed 0BSD. It costs nothing until one of its globs matches a file; then it loads 56 tokens. A static security scan graded it A with 0 findings. It is 100% identical to setup-meta-quest-tools, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
sim
Run the EmbodiedGen simulation rendering workflow with sim-cli.
cert-check
Review the current state against certification and platform compliance expectations.
combat-design
Design or revise combat rules, variables, readability, and tuning direction.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
status
Show 3d-design team status and recent activity.
unity-optimize
Profile and optimize performance — uses MCP profiler for frame timing, memory, rendering stats. Identifies bottlenecks and applies fixes.