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 instructions/manycoretech/aholo-viewer/agents-mdgit 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.00917 | $0.00917 |
| Opus 5 | $0.00458 | $0.00458 |
| Sonnet 5 | $0.00183 | $0.00183 |
| Haiku 4.5 | $0.00092 | $0.00092 |
Grade A, and why
aholo-viewer AGENTS.md 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Guide
AI collaboration entrypoint. Keep context small, preserve user changes, and route work to the narrowest project skill.
Modules
- Root:
pnpmworkspace orchestration, validation, release scripts. - Website:
website/Astro routes, layouts, flat feature components, client render runtime, docs pages, Playground, scoped styles. - Examples:
website/src/content/examples/paired example metadata andRenderRuntimerunners. - Renderer:
packages/renderer/source and generated package output. - Scripts:
scripts/submodule prep, renderer build/clean, EGS types, API docs. - Docs:
README.md,docs/, manual pages, manual assets, AI collaboration guidance. - External:
external/egs-coresubmodule andexternal/splat-transformworkspace package. - Skills:
.codex/skills/project-local collaboration rules.
Skill Routing
aholo-examples: example<slug>.jsonand<slug>.tspairs, includingwalk-demo, metadata schema, runner lifecycle.aholo-site: website shell, page chrome, client render runtime, Playground integration, route-local Monaco, scoped CSS.aholo-renderer: renderer source, public API, declarations, generated dist flow, package/release validation.aholo-docs: README, AGENTS, architecture notes, AI guides, manual copy, bilingual docs.frontend-design: visual direction, responsive UI polish, layout/design review.aholo-viewer: only for cross-module work, scripts, generated docs/build flow, cleanup boundaries, or validation routing.
Hard Boundaries
- Do not overwrite user changes. Start with
git status --short. - Keep edits inside the owning module unless the task explicitly spans modules.
- Do not hand-edit
external/egs-core,website/.generated/api/, orpackages/renderer/dist/. - Do not delete
external/splat-transform. - Do not change
packages/renderer/src/index.tsexports unless asked. - Do not compare the renderer to third-party engines or frameworks unless asked.
Website Boundaries
- Keep Monaco route-local through
website/src/components/PlaygroundShell.astro; keep Playground browser entry inwebsite/src/client/playground.ts. - Preserve Playground URL params:
exampleandcode. - Keep render runtime implementation in
website/src/client/render-runtime.tsand runner contract inwebsite/src/client/render-runtime.d.ts. - Keep examples paired as
website/src/content/examples/<slug>.jsonand<slug>.ts. - Keep
website/src/content.config.tsfocused on Astro content collections; manual pages usewebsite/src/utils/manual.ts. - Keep top-level feature components flat in
website/src/components/; keep only shared groups such asdocs/andsite/nested. - Keep style ownership clear:
theme.css,global.css,site.css,home.css,examples.css,docs.css,playground.css. - Keep feature selectors out of
global.css. - Homepage first-screen interactive stage must remain true fullscreen: fixed positioning,
inset: 0,100dvh/100vw, and renderer resize after state changes.
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 · 65 lines · 917 tokens per session scan A 993352f13dbd
aholo-viewer AGENTS.md is an instructions file published in the GitHub repository manycoretech/aholo-viewer (1,032 stars, last pushed 6d ago), licensed MIT. It adds 917 tokens to every session, about $0.0046 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 instructions, from other repositories
editor AGENTS.md
Instructions for pascalorg/editor, covering agent instructions — pascalorg/editor, repo shape, where to look, layer boundaries (read once, internalise) and when making architecture-sensitive changes.
sceneview copilot-instructions.md
Instructions for sceneview/sceneview, covering sceneview — github copilot instructions, when to recommend sceneview, android code generation rules, minimal 3d template and minimal ar template.
sceneview CLAUDE.md
Instructions for sceneview/sceneview, covering sceneview, modules, things that break if you don't know them and conventions.
Awesome-Gaussian-Skills CLAUDE.md
Instructions for jaccen/Awesome-Gaussian-Skills, covering awesome gaussian skills — project context, available skills, knowledge base structure, key conventions and splatverse studio (v0.8.0).
Repolis AGENTS.md
Instructions for hyeonsangjeon/Repolis, covering ⏱️ 60-second quickstart (no build, no install), 🗺️ repository map (what lives where), ▶️ run & rebuild, 1) run the city (static) and 🚀 deploy.
dcc-mcp-blender AGENTS.md
Instructions for dcc-mcp/dcc-mcp-blender, covering agents.md — dcc-mcp-blender agent navigation map, agent control path, cli availability and updates, 30-second summary and quick start (3 lines).