aholo-viewer: Instructions file for Codex

AGENTS.md

aholo-viewer AGENTS.md is an instructions file for Codex, OpenCode from manycoretech/aholo-viewer. It costs 900 tokens per session, scanned A, original, MIT.

Agent instructions for Aholo Viewer, a pnpm workspace containing a website, renderer packages, examples, documentation, scripts, and external packages. They explain which project skill applies to each area.

In plain words
What is it for?
Use them when working on the website, rendering engine, examples, documentation, build scripts, or external packages. They are especially useful for routing tasks to the project's specialized skills.
Why use it?
They provide a map of the repository and set boundaries for where different kinds of changes belong. This helps an agent choose the right files and preserve the project's build and example structure.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: reads ~/.codex paths; mentions Codex.

This is manycoretech/aholo-viewer's own configuration. It tells Codex and OpenCode how to work on aholo-viewer itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything aholo-viewer configures →

About the project

Aholo Viewer is a renderer for 3D Gaussian Splatting scenes and meshes, using chunked streaming and level-of-detail handling for large 3D data. It is packaged as an npm workspace with documentation and includes skills that help coding agents integrate the renderer.

manycoretech/aholo-viewer · 1,119 stars · on GitHub · aholojs.dev

Reuse

Borrowing it

Nothing to install: this file belongs to manycoretech/aholo-viewer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/manycoretech/aholo-viewer/master/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/manycoretech/aholo-viewer

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for aholo-viewer AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/manycoretech/aholo-viewer/agents-md/github.svg)](https://agentmods.dev/instructions/manycoretech/aholo-viewer/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/manycoretech/aholo-viewer/agents-md"><img src="https://agentmods.dev/badge/instructions/manycoretech/aholo-viewer/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.

agentmods 80×15 button for aholo-viewer AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/manycoretech/aholo-viewer/agents-md"><img src="https://agentmods.dev/badge/instructions/manycoretech/aholo-viewer/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 900 This file is loaded in full into every session.
When invoked 900 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00900 $0.00900
Opus 5.5 $0.00360 $0.00360
Sonnet 5.5 $0.00180 $0.00180
Haiku 4.5 $0.00090 $0.00090

Measured 1mo ago against content hash dd1b1b268652, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

AGENTS.md · 64 lines

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.

Agent Guide

AI collaboration entrypoint. Keep context small, preserve user changes, and route work to the narrowest project skill.

Modules

  • Root: pnpm workspace 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 and RenderRuntime runners.
  • 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-core submodule workspace package.
  • Skills: .codex/skills/ project-local collaboration rules.

Skill Routing

  • aholo-examples: example <slug>.json and <slug>.ts pairs, including walk-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/, or packages/renderer/dist/.
  • Do not change packages/renderer/src/index.ts exports 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 in website/src/client/playground.ts.
  • Preserve Playground URL params: example and code.
  • Keep render runtime implementation in website/src/client/render-runtime.ts and runner contract in website/src/client/render-runtime.d.ts.
  • Keep examples paired as website/src/content/examples/<slug>.json and <slug>.ts.
  • Keep website/src/content.config.ts focused on Astro content collections; manual pages use website/src/utils/manual.ts.
  • Keep top-level feature components flat in website/src/components/; keep only shared groups such as docs/ and site/ 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.

Read the full file on GitHub · 64 lines

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.

  1. 1mo ago Changed · -1 lines · -17 tokens per session dd1b1b268652
  2. 2mo ago First seen · 65 lines · 917 tokens per session scan A 993352f13dbd

Subscribe to this mod's changes

aholo-viewer AGENTS.md is an instructions file published in the GitHub repository manycoretech/aholo-viewer (1,119 stars, last pushed yesterday), licensed MIT. It adds 900 tokens to every session, about $0.0036 per session on Opus 5.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.

Related

aholo-viewer AGENTS.md compared with instructions from other repositories

aholo-viewer AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
aholo-viewer AGENTS.mdmanycoretech/aholo-viewerInstructions file1.1kyesterdayMITA900Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode