What is threejs-cinematic-world-zoom AGENTS.md?

Development guidance for a three.js app that flies a camera from orbit to a landmark on Google's photorealistic 3D map tiles and records the flight as an MP4 video. It describes the commands, code layout, camera moves, lighting, and verification method.

Use it when changing the camera path, lighting, map tiles, assets, recording, or user interface, and when verifying a flight by stepping it through time.

It explains which files control each part of the flight and how to test changes when there is no automated test suite or linter.

How Makio64/threejs-cinematic-world-zoom configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to Makio64/threejs-cinematic-world-zoom. 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/Makio64/threejs-cinematic-world-zoom/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/Makio64/threejs-cinematic-world-zoom

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/makio64/threejs-cinematic-world-zoom/agents-md/github.svg)](https://agentmods.dev/instructions/makio64/threejs-cinematic-world-zoom/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/makio64/threejs-cinematic-world-zoom/agents-md"><img src="https://agentmods.dev/badge/instructions/makio64/threejs-cinematic-world-zoom/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/makio64/threejs-cinematic-world-zoom/agents-md"><img src="https://agentmods.dev/badge/instructions/makio64/threejs-cinematic-world-zoom/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 2,583 This file is loaded in full into every session.

When invoked 2,583 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.

Model	Per session	Once invoked
Fable 5.1	$0.02583	$0.02583
Opus 5	$0.01291	$0.01291
Sonnet 5	$0.00517	$0.00517
Haiku 4.5	$0.00258	$0.00258

Measured 10d ago against content hash 27911be19122, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

threejs-cinematic-world-zoom 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 10d 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 · 215 lines

How it starts

The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Working on this codebase

A three.js app that flies a camera from orbit onto a landmark on Google's photorealistic 3D tiles and records the flight to MP4. Read the README first for what it does; this file is how it is built.

No framework, no build step beyond Vite, no state library. Plain ES modules, plain DOM.

Commands

pnpm install          # also vendors the sky binaries into public/assets
pnpm dev              # vite on :5180
pnpm build            # -> dist/
pnpm assets           # re-vendor public/assets by hand

There is no test suite and no linter. Verify by running it: the flight is the test, and world.seek( t ) will step it without a clock (see Verifying a change).

Layout

src/
  main.js                 wiring only: UI ↔ world ↔ recorder. No logic.
  sun.js                  NOAA solar position, the daylight solve, light presets
  assets.js               local-first asset resolution, CDN fallback
  tilesAuth.js            Cesium Ion / Google Maps key resolution + verification
  camera/
    Rig.js                geographic camera rig, singularity-free
    shots.js              the five moves
    easing.js             curves
  world/
    World.js              renderer, tiles, atmosphere, clouds, the loop
    EffectAdapter.js      pmndrs postprocessing → renderer.setEffects()
    TileCreasedNormalsPlugin.js  local three addon — minify-safe worker alias
  record/Recorder.js      frame-locked WebCodecs capture
  data/landmarks.js       the landmark table, plus text → target
  data/mapLinks.js        pasted map links and codes → lat/lon, offline
  ui/UI.js                all of the DOM
  ui/Venue.js             the conference mark, and its card over the venue
scripts/copy-assets.mjs   vendors the atmosphere and cloud binaries into public/

How a flight works

UI.on.go
  └─ main.launch()
       ├─ world.prepareShot()      solve the sun → derive the end bearing →
       │                           build the shot sampler
       ├─ world.preroll()          ease to the top of the shot while tiles stream
       ├─ world.settle()           pump the tile pipeline until quiet
       ├─ world.autoExpose()       meter 5 points, build an exposure curve
       └─ world.play()             state = 'flying'; the rAF loop samples the
                                   shot by shotTime and applies it to the rig

Read the full file on GitHub · 215 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.

10d ago First seen · 215 lines · 2,583 tokens per session scan A 27911be19122

Subscribe to this mod's changes

threejs-cinematic-world-zoom AGENTS.md is an instructions file published in the GitHub repository Makio64/threejs-cinematic-world-zoom (150 stars, last pushed 1mo ago), licensed MIT. It adds 2,583 tokens to every session, about $0.0129 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.

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.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

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

microsoft/vscode · 6,785 tokens

threejs-cinematic-world-zoom: Instructions file for Codex