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 skills/meta-quest/agentic-tools/hz-spatial-sdknpx skills add meta-quest/agentic-tools --skill hz-spatial-sdkgit clone --depth 1 https://github.com/meta-quest/agentic-toolsWrote 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/skills/meta-quest/agentic-tools/hz-spatial-sdk)<a href="https://agentmods.dev/skills/meta-quest/agentic-tools/hz-spatial-sdk"><img src="https://agentmods.dev/badge/skills/meta-quest/agentic-tools/hz-spatial-sdk.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.00045 | $0.02494 |
| Opus 5 | $0.00023 | $0.01247 |
| Sonnet 5 | $0.00009 | $0.00499 |
| Haiku 4.5 | $0.00005 | $0.00249 |
Grade A, and why
hz-spatial-sdk 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 5d 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 — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spatial SDK Skill
Build native Android spatial applications for Meta Quest using the Meta Spatial SDK. This skill covers the Entity-Component-System architecture, 2D panel rendering, 3D object placement, hybrid app development, and deployment to Horizon OS devices.
When to Use This Skill
Use this skill when you need to:
- Build a native Android app for Meta Quest using the Spatial SDK and Kotlin
- Create hybrid experiences that combine 2D Android UI panels with 3D content
- Work with the Entity-Component-System (ECS) architecture in Spatial SDK
- Add 3D objects, animations, or spatial interactions to a Quest application
- Configure panels using Jetpack Compose or Android Views for spatial rendering
- Use the Spatial Editor to compose 3D scenes visually
- Deploy and test Spatial SDK applications on a Quest device
This skill applies to all Meta Quest headsets running Horizon OS (Quest 2, Quest 3, Quest 3S, Quest Pro).
What is Meta Spatial SDK
Meta Spatial SDK is Meta's native Android framework for building spatial applications on Horizon OS. It extends the standard Android development model with spatial capabilities, allowing developers to write apps in Kotlin that render 2D UI panels in 3D space, display glTF models, handle spatial input, and integrate with Horizon OS features like passthrough, scene understanding, and hand tracking.
Unlike Unity or Unreal Engine, Spatial SDK builds on top of the Android Activity lifecycle. Applications are standard Android APKs that use Spatial SDK libraries to gain spatial rendering and interaction capabilities.
Key characteristics:
- Kotlin-first: all application logic is written in Kotlin
- Android-native: builds on standard Android Activity, Gradle, and Jetpack libraries
- ECS architecture: entities, components, and systems manage 3D scene state
- Panel rendering: Android UI frameworks (Jetpack Compose, Views) render as spatial panels
- Gradle integration: Spatial SDK ships as AAR libraries pulled via Gradle dependencies
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 284 lines · 45 tokens per session scan A 6c9dc83368c7
hz-spatial-sdk is a skill published in the GitHub repository meta-quest/agentic-tools (188 stars, last pushed 14d ago), licensed Apache-2.0. It adds 45 tokens to every session and 2,494 once invoked, about $0.0002 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 skills, from other repositories
android-phone-control
Control an Android phone from a local Termux/Linux host using a deterministic ADB toolkit: device checks, wake/unlock/session mode, screenshots, UI dumps, taps, text input, key events, app launch, and safe app smoke tests.
developer-device-platform-basics
Provides guidance and instructions on managing remote devices on Developer Device Platform (DDP). Use when reserving remote Android devices, establishing connection tunnels, checking session status, or extending/cancelling leases. Don't use for iOS or local device/hardware inquiries.
camerax
Provide technical guidance for Android camera development with CameraX. Use when implementing camera features, handling asynchronous recording lifecycles, wiring low-level hardware interop using CameraX, or integrating ML Kit or Media3 effects.
analyzing-binaries
Reverse engineer compiled binaries, firmware, and mobile app packages using triage, static disassembly, decompilation, and dynamic instrumentation. Use when analyzing an executable, ELF/PE/Mach-O file, firmware image, or stripped binary, recovering an algorithm or protocol, or working a CTF reversing challenge.
android-adb-control
Direct control of Android physical devices and Termux environments via Android Debug Bridge (ADB).
droidlume-control
Operate DroidLume-managed Android devices through the structured DroidLume CLI. Use for creating, starting, stopping, configuring, snapshotting, inspecting, repairing, and screenshotting devices; installing or launching APKs; sending Android input; and collecting diagnostics.