Borrowing it
Nothing to install: this file belongs to J-o-n-a-t-h-a-n-M-u-e-l-l-e-r/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.
curl -O https://raw.githubusercontent.com/J-o-n-a-t-h-a-n-M-u-e-l-l-e-r/lattice/main/AGENTS.mdgit clone --depth 1 https://github.com/J-o-n-a-t-h-a-n-M-u-e-l-l-e-r/latticeWrote 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.
[](https://agentmods.dev/instructions/j-o-n-a-t-h-a-n-m-u-e-l-l-e-r/lattice/agents-md)<a href="https://agentmods.dev/instructions/j-o-n-a-t-h-a-n-m-u-e-l-l-e-r/lattice/agents-md"><img src="https://agentmods.dev/badge/instructions/j-o-n-a-t-h-a-n-m-u-e-l-l-e-r/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.
<a href="https://agentmods.dev/instructions/j-o-n-a-t-h-a-n-m-u-e-l-l-e-r/lattice/agents-md"><img src="https://agentmods.dev/badge/instructions/j-o-n-a-t-h-a-n-m-u-e-l-l-e-r/lattice/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.01294 | $0.01294 |
| Opus 5 | $0.00647 | $0.00647 |
| Sonnet 5 | $0.00259 | $0.00259 |
| Haiku 4.5 | $0.00129 | $0.00129 |
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 11d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — how to work in this repo
Read this before changing anything. It applies to Copilot coding agent, Claude Code, and any other agent working here.
What this project is
Lattice reads a repo's issues, infers the dependency graph between them, stores it, and serves the resulting schedule over a REST API (to the web UI) and MCP (to coding agents). It runs automatically on issue events and a schedule — no approval step, no button.
GitHub is a data source, not a data store. Lattice never writes to it.
Two services in one npm-workspaces monorepo: apps/backend (pipeline, store, REST, MCP) and apps/web (the interactive graph). apps/web consumes the REST API and holds no database URL, GitHub token or model key. See README.md for the pitch and docs/01-architecture.md for the component map.
Ground rules
- Never write to GitHub. No dependency writes, no comments, no labels, no issue edits. Reads only. This is what makes an unsupervised system safe to run, and it is not negotiable for convenience.
- The full graph lives in the store. Every edge, above and below the blocking threshold. The one destructive step is cycle breaking, and it is recorded. Transitive reduction is a rendering choice — never store the reduced graph.
- The DAG invariant is load-bearing.
makeAcyclic()must throw if the graph is still cyclic after cycle-breaking. Never weaken that assertion to make a test pass. - Every inferred edge carries verbatim evidence, validated against source text. Nothing downstream re-checks it — an edge whose evidence can't be verified is one nobody can audit after it has been written to a real issue. Guard it.
- Read before you write. Check
docs/09-github-api-notes.mdbefore touching any GitHub call — several endpoints have non-obvious requirements that will silently produce wrong behaviour.
Working on an issue
- The issue title is prefixed with its workstream (
[F],[G],[I],[S],[U],[M],[C],[X]). Seedocs/06-workstreams.md. - Issue bodies state their own dependencies in prose ("depends on", "blocked by"). Respect them — if your issue depends on a type or interface another issue defines, and that issue isn't done, say so rather than inventing a competing shape.
- Stay inside the files listed under Scope in the issue body. Five people and several agents are working this repo in parallel; the scope list is the collision-avoidance mechanism.
- If you discover the issue is genuinely blocked by something not listed, say so and stop rather than expanding scope. If the Lattice MCP server is available, call
report_dependencyso the graph learns it.
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.
- 11d ago First seen · 66 lines · 1,294 tokens per session scan A d94ba2909508
lattice AGENTS.md is an instructions file published in the GitHub repository J-o-n-a-t-h-a-n-M-u-e-l-l-e-r/lattice (0 stars, last pushed 17d ago), licensed MIT. It adds 1,294 tokens to every session, about $0.0065 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-31.
Other instructions, from other repositories
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.
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.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).