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 agents/manycoretech/aholo-viewer/claudegit clone --depth 1 https://github.com/manycoretech/aholo-viewerWhat 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.00000 | $0.00640 |
| Opus 5 | $0.00000 | $0.00320 |
| Sonnet 5 | $0.00000 | $0.00128 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
claude 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Instructions: Use Aholo Viewer
Use these instructions when Claude is helping a user integrate the public @manycore/aholo-viewer npm package into a browser application.
Activation
Apply this guidance when the user asks Claude to install, bootstrap, debug, or extend an app that uses @manycore/aholo-viewer, especially for:
- 3D Gaussian Splatting (3DGS) rendering.
- Mesh rendering with
BufferGeometry,Mesh, lights, and materials. - Viewer setup, camera setup, scene composition, render-loop wiring, or cleanup.
- React, Vue, Svelte, Vite, or plain TypeScript browser integrations.
Read First
Before writing non-trivial code, read the AI-facing docs listed by https://aholojs.dev/llms.txt.
Preferred reading order:
https://aholojs.dev/llm/manual/getting-started.mdhttps://aholojs.dev/llm/manual/basic-concepts.mdhttps://aholojs.dev/llm/api/index.mdhttps://aholojs.dev/llm/examples/index.md
Use the Markdown docs instead of scraping rendered HTML.
Implementation Rules
- Import only public exports from
@manycore/aholo-viewer; never import internal@qunhe/*packages. - Create a stable application-owned container before calling
createViewer(...). - Attach DOM event listeners to the container or another app-owned element, not to the engine canvas.
- Do not persistently store the engine canvas. If canvas access is unavoidable, read it only at the point of use and discard the reference immediately.
- Use
PerspectiveCameraorOrthographicCamera, then callviewer.setCamera(camera). - Add objects to
viewer.getScene(). - Configure the pipeline with
setViewerConfig(viewer, { pipeline: ... }). - Trigger rendering with
viewer.render()or schedule rendering throughviewer.requestRenderHandler. - Do not construct
Splatdirectly; load splat data withSplatLoaderand create renderable splats withSplatUtils.createSplat(...).
Cleanup Rules
- Stop render loops, event listeners, controls, and pending async work before releasing resources.
- Use
freeGPU()to release an object's own GPU resources while keeping the object reusable. - Use
freeAllGpuResourceOwned()when owned child resources should also release GPU state. For example,geometry.freeAllGpuResourceOwned()also releases attribute and index GPU resources. - Use
destroy()only for final teardown after the object is detached from the scene and no callback, async task, viewport, material, geometry, or app state can use it again.
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 · 51 lines · 0 tokens per session scan A 362d70783f3d
claude is an agent published in the GitHub repository manycoretech/aholo-viewer (1,032 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 640 tokens. 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 agents, from other repositories
component-example-creator
Use this agent when the user requests examples for a component, asks to add stories to a component, needs documentation examples updated, or mentions creating/updating component demonstrations. Examples:\n\n \nContext: User is working on the Checkbox component and wants to add new usage examples.\nuser: "Can you…
frontend-reviewer
Use when reviewing changes to UI components, hooks, client state, or rendering logic (React/Vue/Svelte) — verifies component correctness, state topology, and render purity against the frontend and ui persona standards.
frontend-developer
Build and optimize frontend applications with expertise in React, Vue, and modern web standards. Specializes in UI/UX implementation, component architecture, state management, accessibility, and responsive design.
frontend-specialist
Senior Frontend Architect for React, Next.js, Vue, and modern web systems. Use for UI components, styling, state management, responsive design, accessibility. Triggers: component, react, vue, ui, ux, css, tailwind, responsive, nextjs.
frontend-engineer
Generates production-grade frontend code (React, Next.js, Vue, Blade+Alpine, vanilla HTML, Astro) with anti-AI-slop discipline. Dispatched by /ux-design, /ux-component, /ux-dashboard, /ux-fix. Owns implementation; the calling command owns orchestration and review.
storybook-debugger
Use this agent when you need to debug and fix issues in the HeroUI Storybook development environment, particularly CSS transformation errors, Tailwind CSS v4 compatibility issues, or component styling problems. This includes investigating build errors, runtime errors in the browser, and issues with the CSS-to-JS…