CloudXR.js is a JavaScript client SDK and sample applications for displaying streamed virtual- and augmented-reality content from CloudXR servers in web browsers on XR devices. Developers use it to build browser clients while a GPU-equipped server renders the spatial scene and receives head and hand tracking data. The catalogue entries cover the sample clients and guidance for working with the SDK.
Borrowing it
Nothing to install: this file belongs to NVIDIA/cloudxr-js-samples. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/NVIDIA/cloudxr-js-samples/main/AGENTS.mdgit clone --depth 1 https://github.com/NVIDIA/cloudxr-js-samplesWrote 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/instructions/nvidia/cloudxr-js-samples/agents-md)<a href="https://agentmods.dev/instructions/nvidia/cloudxr-js-samples/agents-md"><img src="https://agentmods.dev/badge/instructions/nvidia/cloudxr-js-samples/agents-md/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/instructions/nvidia/cloudxr-js-samples/agents-md"><img src="https://agentmods.dev/badge/instructions/nvidia/cloudxr-js-samples/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.02827 | $0.02827 |
| Opus 5.5 | $0.01131 | $0.01131 |
| Sonnet 5.5 | $0.00565 | $0.00565 |
| Haiku 4.5 | $0.00283 | $0.00283 |
Grade A, and why
cloudxr-js-samples AGENTS.md scanned grade A with 1 finding 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 18d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fL -o "${SDK_FILE}" \ How it starts
The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NVIDIA CloudXR.js — Agent Instructions
Applies to: AI agents helping a user consume the CloudXR.js SDK in a sample/integration app. Read this when: Touching sample files, scaffolding a new client app, or answering "how do I integrate
@nvidia/cloudxrin my app?". For working on the SDK source itself, see the repo-root AGENTS.md. For detailed API types, see agent-api-reference.md. For a coding-focused quick reference, see SKILL.md.
What This Is
CloudXR.js is a TypeScript SDK that streams VR/AR from a GPU server to a web browser via WebRTC. The server renders; the browser displays video and sends back head/hand tracking.
Code Quality
All new and modified code in the repo must meet these standards before merge.
Formatting and lint
- Conform to Prettier and ESLint.
- Before push, run:
npm run format:check # verify npm run format # auto-fix lint + Prettier - Common failures: Prettier drift in touched files,
import/orderviolations.
Documentation
- Every named function, method, class, and interface must have a JSDoc block (
/** … */) describing its purpose. Use@param,@returns, and@throwswhere they add clarity. Arrow functions and anonymous function expressions do not require JSDoc, but should still have concise inline comments when they introduce a logical code block. - Tests:
describeblocks,it/testcases, callbacks, and local test helpers do not require JSDoc. Test function names and assertions should be strongly readable from their definitions; prefer renaming or clearer assertions over adding JSDoc in test files. - Inside every function or method body you add or change, each logical step must have a short
//comment on the line immediately above the code it describes. A logical step includes: guards and early returns, branches (if/else), loops, I/O (send, parse, read, write), mutations (assign, push, delete, clear), and cleanup. - Blank-line rule: put one empty line before each
//comment and one empty line before the next code step when the previous step ended with code (not a comment). Match the spacing inexamples/hub/src/hub/cors.ts. - Comments explain why, protocol, or constraints — not what the syntax literally does. Do not restate the code (
// increment i). - Complex logic (non-obvious control flow, wire formats, timing, security) must have enough comment context that a reader unfamiliar with the file can follow without guessing.
- Before finishing: scan each edited function body top to bottom; if any logical step has no comment directly above it, add one.
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.
- 18d ago Changed · +93 lines · +1,110 tokens per session d1103c833c5e
- 2mo ago First seen · 139 lines · 1,717 tokens per session scan A 857c78ea8079
cloudxr-js-samples AGENTS.md is an instructions file published in the GitHub repository NVIDIA/cloudxr-js-samples (25 stars, last pushed 18d ago), licensed Apache-2.0. It adds 2,827 tokens to every session, about $0.0113 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.