lattice: Instructions file for Codex

AGENTS.md

lattice AGENTS.md is an instructions file for Codex, OpenCode from plausibleventures/lattice. It costs 3,095 tokens per session, scanned A, original, MIT.

Repository instructions for Lattice, a TypeScript toolkit for building isometric games whose behavior can be replayed consistently. An isometric game shows a three-dimensional-looking world from an angled view.

In plain words
What is it for?
Use them before changing the repository, especially when working on its nine libraries, game code, deterministic random behavior, or build process.
Why use it?
They define rules that keep game results repeatable and explain where to find packages, tasks, state, and cross-package contracts.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is plausibleventures/lattice's own configuration. It tells Codex and OpenCode how to work on lattice 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 lattice configures →

Reuse

Borrowing it

Nothing to install: this file belongs to plausibleventures/lattice. 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/plausibleventures/lattice/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/plausibleventures/lattice

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 lattice AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/plausibleventures/lattice/agents-md"><img src="https://agentmods.dev/badge/instructions/plausibleventures/lattice/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 3,095 This file is loaded in full into every session.
When invoked 3,095 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.03095 $0.03095
Opus 5.5 $0.01238 $0.01238
Sonnet 5.5 $0.00619 $0.00619
Haiku 4.5 $0.00310 $0.00310

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

Security

Grade A, and why

lattice 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 · 220 lines

How it starts

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

Lattice — how to work in this repo

Lattice is a kit for building isometric, deterministic, zero-asset games in TypeScript. Nine small libraries that compose, and a real game built from nothing but them.

This file is the constitution. It is written for agents first and humans second, because agents outnumber humans here. Read it before you touch anything. It is short on purpose.

  • What each package is → .lattice/kit.json (machine-readable), README.md § The nine packages, and each package's own README.md. The cross-package contracts are in docs/SEAMS.md
  • What to work on next → .lattice/tasks.json
  • Where the build is → .lattice/state.json
  • How one work cycle runs → docs/LOOP.md

The eleven non-negotiables

These are not preferences. A change that breaks one of these is reverted, not debated.

  1. Determinism is a feature, not an accident. Math.random(), Date.now(), and performance.now() are banned inside every package's src/. Randomness comes from a seeded Rng passed in by the caller; time arrives as a parameter. This is enforced by npm run lint. A game built on Lattice must be able to replay a session from a seed and an input log and land on the same pixel.

    And it has two tiers, because the language only promises so much. ECMA-262 specifies + - * /, Math.sqrt, Math.imul and the bitwise operators exactly. It explicitly does not require sin, cos, pow, exp or log to be correctly rounded, so two conforming engines may disagree in the last bit.

    arithmetic promise may reach
    Tier A + - * /, sqrt, imul, bitwise bit-identical on every engine hashes, save files, replays, anything
    Tier B sin, cos, pow, exp, log, … correct to within an ulp or so pixels only — never hashed, never persisted

    Tier B is not banned; a cost curve is b · r^k and there is no honest way around that. It is required to declare itself: mark the site @tier-b and the linter is satisfied. That makes every one of them greppable, so an auditor can ask of each in turn whether it ever reaches a save file.

Read the full file on GitHub · 220 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 First seen · 220 lines · 3,095 tokens per session scan A e382ba853b2b

Subscribe to this mod's changes

lattice AGENTS.md is an instructions file published in the GitHub repository plausibleventures/lattice (40 stars, last pushed 1mo ago), licensed MIT. It adds 3,095 tokens to every session, about $0.0124 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

Other instructions, from other repositories

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 · 9,649 tokens

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,257 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,159 tokens