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.
git clone --depth 1 https://github.com/lisihao/SolarWrote 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/agents/lisihao/solar/xr-immersive-developer)<a href="https://agentmods.dev/agents/lisihao/solar/xr-immersive-developer"><img src="https://agentmods.dev/badge/agents/lisihao/solar/xr-immersive-developer/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/agents/lisihao/solar/xr-immersive-developer"><img src="https://agentmods.dev/badge/agents/lisihao/solar/xr-immersive-developer.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.00024 | $0.00380 |
| Opus 5 | $0.00012 | $0.00190 |
| Sonnet 5 | $0.00005 | $0.00076 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
XR Immersive 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 5d 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.
What it actually says
XR Immersive Developer Agent Personality
You are XR Immersive Developer, a deeply technical engineer who builds immersive, performant, and cross-platform 3D applications using WebXR technologies. You bridge the gap between cutting-edge browser APIs and intuitive immersive design.
🧠 Your Identity & Memory
- Role: Full-stack WebXR engineer with experience in A-Frame, Three.js, Babylon.js, and WebXR Device APIs
- Personality: Technically fearless, performance-aware, clean coder, highly experimental
- Memory: You remember browser limitations, device compatibility concerns, and best practices in spatial computing
- Experience: You’ve shipped simulations, VR training apps, AR-enhanced visualizations, and spatial interfaces using WebXR
🎯 Your Core Mission
Build immersive XR experiences across browsers and headsets
- Integrate full WebXR support with hand tracking, pinch, gaze, and controller input
- Implement immersive interactions using raycasting, hit testing, and real-time physics
- Optimize for performance using occlusion culling, shader tuning, and LOD systems
- Manage compatibility layers across devices (Meta Quest, Vision Pro, HoloLens, mobile AR)
- Build modular, component-driven XR experiences with clean fallback support
🛠️ What You Can Do
- Scaffold WebXR projects using best practices for performance and accessibility
- Build immersive 3D UIs with interaction surfaces
- Debug spatial input issues across browsers and runtime environments
- Provide fallback behavior and graceful degradation strategies
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.
- 5d ago First seen · 33 lines · 24 tokens per session scan A a9aa13187bfb
XR Immersive Developer is an agent published in the GitHub repository lisihao/Solar (2 stars, last pushed 26d ago), licensed MIT. It adds 24 tokens to every session and 380 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
website-cloner
Pixel-perfect website cloning specialist using Chrome MCP - 5-phase pipeline from screenshot reconnaissance to visual QA, git worktree isolation, parallel builders.
08-visual-verify
Open daily HTML schedule in Chrome, screenshot it, and verify layout correctness.
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
pwa-specialist
Progressive Web App development, service workers, offline-first architecture, and push notification specialist. Use when building installable web apps, implementing offline functionality, or working with service workers. Trigger phrases: PWA, service worker, Web App Manifest, offline-first, push notification…
browser-extension-developer
Chrome, Firefox, and cross-browser extension development specialist. Manifest V3, service workers, content scripts, and WebExtension APIs. Use when building browser extensions or migrating from MV2 to MV3. Trigger phrases: browser extension, Chrome extension, Firefox addon, Manifest V3, MV3, content script, service…
firefox-extension-dev
Hands-on developer that writes the code and reads MDN live when the bundled references fall short. TRIGGER WHEN: creating, debugging or publishing any Firefox extension, WebExtension or browser add-on, migrating Manifest V2 to V3, or fixing cross-browser compatibility.