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/facebookresearch/projectaria-plugins/vrs-clinpx skills add facebookresearch/projectaria-plugins --skill vrs-cligit clone --depth 1 https://github.com/facebookresearch/projectaria-pluginsWhat 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.00130 | $0.01032 |
| Opus 5 | $0.00065 | $0.00516 |
| Sonnet 5 | $0.00026 | $0.00206 |
| Haiku 4.5 | $0.00013 | $0.00103 |
Grade A, and why
vrs-cli 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 2d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Native VRS CLI
VRS is Meta's open container format for timestamped multi-modal sensor data — every Aria recording is one VRS file. The native VRS library ships a CLI (vrs) for inspecting and manipulating VRS files at the file / stream level. It is a separate codebase from projectaria-tools (PAT) and is not Aria-aware.
VRS source + install instructions: https://github.com/facebookresearch/vrs Aria-specific VRS notes: https://facebookresearch.github.io/projectaria_tools/gen2/technical-specs/vrs/data-format
When to use VRS CLI vs PAT vs vrs-health-check
| Goal | Use |
|---|---|
| Validate that a VRS file is not corrupted | vrs check |
| Inspect a VRS file (streams, record counts) | vrs CLI |
| Slice / extract / copy streams at the file level | vrs CLI |
| Read decoded sensor data (images, IMU samples in physical units) | PAT — see the projectaria-tools skill |
| Anything that needs camera calibration / projection | PAT |
| Aria-specific recording quality (drop rates, timing checks) | vrs-health-check (a different tool, despite the name overlap) |
The CLI does not understand Aria-specific semantics — StreamId→label mapping, the factory_calibration JSON, profile names, MPS outputs, etc. It only knows about VRS streams and records.
Install
The CLI lives in the VRS GitHub repository. Follow the README at https://github.com/facebookresearch/vrs for current build and install instructions — they cover supported package managers, building from source, and per-OS dependencies. Use the latest main if you hit unsupported-feature errors against a newer Aria recording.
HEVC decoder is required for image-related operations. Aria VRS files use H.265 / HEVC for camera streams. On most Linux distros, installing ffmpeg from the system package manager pulls in HEVC support. See the VRS README for the specific FFmpeg version / build flags it expects.
Usage — defer to --help
The CLI is self-documenting. Always run:
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.
- 2d ago First seen · 64 lines · 130 tokens per session scan A 17727cb906a8
vrs-cli is a skill published in the GitHub repository facebookresearch/projectaria-plugins (8 stars, last pushed 7d ago), licensed Apache-2.0. It adds 130 tokens to every session and 1,032 once invoked, about $0.0006 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…