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 skills add meta-quest/agentic-tools --skill hz-android-2d-portinggit 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-android-2d-porting)<a href="https://agentmods.dev/skills/meta-quest/agentic-tools/hz-android-2d-porting"><img src="https://agentmods.dev/badge/skills/meta-quest/agentic-tools/hz-android-2d-porting/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/meta-quest/agentic-tools/hz-android-2d-porting"><img src="https://agentmods.dev/badge/skills/meta-quest/agentic-tools/hz-android-2d-porting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 35 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 38 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 35 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00080 | $0.01814 |
| Opus 5.5 | $0.00032 | $0.00726 |
| Sonnet 5.5 | $0.00016 | $0.00363 |
| Haiku 4.5 | $0.00008 | $0.00181 |
Grade A, and why
hz-android-2d-porting 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 1mo 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Android 2D App Porting to Horizon OS
When to Use
Use this skill when:
- Porting an existing Android 2D app to run on Meta VR headsets
- Adapting a mobile Android app for Horizon OS panels
- Troubleshooting input, layout, or compatibility issues with a 2D app on Meta VR devices
- Preparing an Android app for Horizon Store submission
- Evaluating whether an existing Android app is compatible with Horizon OS
Overview
Horizon OS is built on Android (AOSP) and can run standard Android applications inside panels -- floating 2D windows positioned in 3D space. Most well-built Android apps work on Meta VR devices with minimal changes, but several areas require attention:
- Input: There is no touchscreen. Users interact via controller pointer (ray-casting), hand tracking, or connected peripherals.
- Layout: Apps run in resizable panels, not full-screen on a fixed display.
- Compatibility: Dependencies and permissions must work without Google Play Services or unavailable hardware.
- Design and performance: Apps must meet Horizon Store requirements on mobile hardware.
The goal of porting is to make the app feel native to the Meta VR experience while preserving existing functionality.
Porting Workflow
Step 1: Initial Testing
Build and install the existing app with its normal Android workflow. Android Studio, Gradle, and adb all work with a connected Meta VR device:
./gradlew installDebug
adb shell am start -n com.example.yourapp/.MainActivity
Prefer metavr app install <apk> and metavr app launch <package> over raw adb here, then stream metavr adb logcat --follow during this first run. Note any immediate crashes, black screens, input problems, or layout breakage.
Step 2: Compatibility Audit
Check whether the app depends on Google Play Services, unsupported hardware, or prohibited permissions before changing its UI. Make unsupported features optional or replace them with Horizon OS alternatives. See Compatibility Requirements.
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.
- 1mo ago Changed · -17 lines · +34 tokens per session 411dadad4dc3
- 2mo ago First seen · 187 lines · 46 tokens per session scan A 9e65afcfd231
hz-android-2d-porting is a skill published in the GitHub repository meta-quest/agentic-tools (245 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 80 tokens to every session and 1,814 once invoked, about $0.0003 per session on Opus 5.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.
hz-android-2d-porting compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| hz-android-2d-portingmeta-quest/agentic-tools | Skill | 245 | 1mo ago | Apache-2.0 | A | 80 | Claude Code |
| mobileclimobile-next/mobilecli | Skill | 314 | yesterday | none | B | 162 | Claude Code |
| android-phone-controlpatrickdass93/android-phone-control-skill | Skill | 19 | 5mo ago | MIT | A | 53 | Claude Code, Codex |
| android-ui-journey-testinglingxling/awesome-skills-cn | Skill | 329 | 1mo ago | MIT | A | 27 | Claude Code |
| android-cliGhosteken/agent-harness | Skill | 1 | 4d ago | MIT | C | 30 | Claude Code |
| unity-platform-player-settingsrachitkumarrastogi/unity-mcp-server | Skill | 5 | 3mo ago | none | A | 39 | Claude Code, Codex |
| unity-firebase-mobilerachitkumarrastogi/unity-mcp-server | Skill | 5 | 3mo ago | none | A | 34 | Claude Code, Codex |