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/tomkrikorian/visionosagents/usdkit-runtime-developernpx skills add tomkrikorian/visionOSAgents --skill usdkit-runtime-developergit clone --depth 1 https://github.com/tomkrikorian/visionOSAgentsWhat 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.00075 | $0.00649 |
| Opus 5 | $0.00037 | $0.00324 |
| Sonnet 5 | $0.00015 | $0.00130 |
| Haiku 4.5 | $0.00007 | $0.00065 |
Grade A, and why
usdkit-runtime-developer 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 3d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
USDKit Runtime Developer
Quick Start
Use this skill for in-process USD stage work from Swift. For hand-authored
.usda edits, package inspection, CLI conversion, or usdchecker validation,
switch to $usd-editor.
- Confirm the target uses the 27 SDKs and can
import USDKit. - Decide whether the task belongs to runtime USDKit or the
usd*command-line asset pipeline. - Load the USDKit decision reference, then the USDKit framework reference.
- Keep
USDStage,USDPrim,USDLayer, and nested property work on one actor; these types are not Sendable. - For live RealityKit display, use
USDStageComponentfrom the RealityKit skill; for Spatial Preview streaming, keep$spatial-preview-developer.
Load References When
| Reference | When to Use |
|---|---|
usdkit-vs-cli.md |
When choosing between runtime USDKit and the command-line USD pipeline. |
usdkit-framework.md |
When using USDStage, USDPrim, USDLayer, observers, export, or package APIs. |
visionos-runtime-loading.md |
When checking how authored USD or USDZ content loads inside a visionOS app. |
apple-runtime-boundaries.md |
When deciding whether to edit authored USD, load through RealityKit, or validate for Apple platforms. |
Workflow
- Identify the owner: runtime Swift-edited stage, authored asset, or package pipeline.
- Use USDKit for in-process stage editing, observation, live rendering, or runtime package export.
- Keep CLI validation in the asset pipeline; USDKit does not replace
usdchecker --arkit --strict. - Preserve authored assets as source of truth unless the task is explicitly procedural or runtime-generated.
Guardrails
- Do not use USDKit just to inspect or batch-convert files in CI; use the CLI
tools through
$usd-editor. - Do not assume beta USDKit symbols are stable; re-check the installed 27 SDK before shipping.
- Do not recreate authored Reality Composer Pro content in Swift unless the feature explicitly requires procedural authoring.
What ships with it
5 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.
- 3d ago First seen · 59 lines · 75 tokens per session scan A 57ed0e38e0e0
usdkit-runtime-developer is a skill published in the GitHub repository tomkrikorian/visionOSAgents (60 stars, last pushed 2mo ago), licensed MIT. It adds 75 tokens to every session and 649 once invoked, about $0.0004 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
gamified-app
A multi-frame gamified mobile-app prototype — three phone frames on a dark showcase stage. Frame 1: cover / poster, Frame 2: today's quests with XP ribbons and a level bar, Frame 3: quest detail. Vivid quest tiles, level ribbon, bottom tab bar. Use when the brief asks for a "gamified app", "habit tracker", "RPG-style…
mobile-games
Mobile game development principles. Touch input, battery, performance, app stores.
build-mobile-threejs-games
Build, tune, or test a Three.js game for mobile web. Use for touch movement, action controls, target selection, touch inventory, safe areas, portrait/landscape layouts, responsive HUD, battery/performance budgets, and real mobile browser QA.
building-mobile-game
Build mobile games and game-like interactive experiences in React Native and Expo. Use when Codex is creating or refactoring arcade, puzzle, casual, action, physics-based, or animation-heavy gameplay, including Expo game setup with the with-reanimated template, sprite-sheet generation and extraction, frame-based…
hz-android-2d-porting
Guides porting existing Android 2D apps to Meta Quest and Horizon OS — input adaptation, panel layout, and design requirements. Use when adapting a mobile Android app for Quest.
hz-new-project-creation
Scaffolds new Meta Quest and Horizon OS projects with recommended settings for Unity, Unreal, Android/Spatial SDK, or WebXR. Use when creating a new Quest app from scratch.