Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add meta-quest/agentic-tools/plugin install 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-psdk-integration)<a href="https://agentmods.dev/skills/meta-quest/agentic-tools/hz-psdk-integration"><img src="https://agentmods.dev/badge/skills/meta-quest/agentic-tools/hz-psdk-integration.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.00107 | $0.02821 |
| Opus 5 | $0.00053 | $0.01411 |
| Sonnet 5 | $0.00021 | $0.00564 |
| Haiku 4.5 | $0.00011 | $0.00282 |
Grade A, and why
hz-psdk-integration 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 6d 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 — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PSDK Feature Integration Wizard
This skill requires interactive mode. It is a multi-step wizard that asks questions and waits for your answers at each step. Do not run this skill with
claude -p(non-interactive/print mode) — it will not work correctly. Use an interactive Claude Code session instead.
You are an interactive integration wizard that helps developers add Horizon Platform SDK (PSDK) features to their Android/Quest applications. Follow the steps below exactly in order. Never skip a step. Never guess missing information — always ask.
Interactive mode check: If you detect that you are running in non-interactive mode (no ability to ask the user questions and wait for responses), immediately stop and inform the user: "This skill requires interactive mode. Please start an interactive Claude Code session and invoke the skill again."
Important References
Before advising on any specific PSDK feature, read the relevant reference files from this skill's references/ directory:
common-setup.md— shared setup, initialization, status codes (ALWAYS read first)<feature>.md— per-feature API reference (e.g.,leaderboards.md,iap.md)
Prerequisites
- metavr (Meta VR CLI) — invoke via
metavr <args>(published as the npm packagemetavr; ifmetavris not on PATH, runnpx -y metavr <args>) - A Meta Quest developer account: https://developer.meta.com/
- An Android project with Gradle build system
Step 0 — Introduction
Present this to the user:
Horizon Platform SDK (PSDK) is Meta's cross-platform SDK that gives Quest apps access to platform services. It provides Android/Kotlin APIs for:
Category Features Identity & Social Users, Entitlements, User Age Category Engagement Achievements, Leaderboards Commerce In-App Purchases (IAP) Presence & Multiplayer Group Presence, Rich Presence Communication Notifications, Push Notifications Content & Media Asset Files App Lifecycle Application, Application Lifecycle Trust & Safety Abuse Report, Consent, Device Application Integrity Misc Language Pack, Rate and Review I'll help you figure out which features fit your app, plan the integration, and implement them step by step.
What ships with it
20 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.
- references/abuse-report.md 2.5 KB
- references/achievements.md 22 KB
- references/application-lifecycle.md 17 KB
- references/application.md 23 KB
- references/architecture-patterns.md 5.9 KB
- references/asset-file.md 22 KB
- references/common-setup.md 4.7 KB
- references/consent.md 15 KB
- references/device-application-integrity.md 10 KB
- references/entitlements.md 9.9 KB
- references/group-presence.md 31 KB
- references/iap.md 21 KB
- references/language-pack.md 16 KB
- references/leaderboards.md 22 KB
- references/notifications.md 17 KB
- references/push-notification.md 4.4 KB
- references/rate-and-review.md 10 KB
- references/rich-presence.md 15 KB
- references/user-age-category.md 11 KB
- references/users.md 13 KB
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.
- 6d ago First seen · 311 lines · 107 tokens per session scan A 7cfbe3d81935
hz-psdk-integration is a skill published in the GitHub repository meta-quest/agentic-tools (189 stars, last pushed 15d ago), licensed Apache-2.0. It adds 107 tokens to every session and 2,821 once invoked, about $0.0005 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.