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/.github/copilot-instructions.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/copilot-instructions)<a href="https://agentmods.dev/instructions/j-o-n-a-t-h-a-n-m-u-e-l-l-e-r/lattice/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/j-o-n-a-t-h-a-n-m-u-e-l-l-e-r/lattice/copilot-instructions/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/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/j-o-n-a-t-h-a-n-m-u-e-l-l-e-r/lattice/copilot-instructions.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.00654 | $0.00654 |
| Opus 5 | $0.00327 | $0.00327 |
| Sonnet 5 | $0.00131 | $0.00131 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
lattice copilot-instructions.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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot instructions
Read AGENTS.md first. It is the canonical guide for every agent in this repo and this file does not repeat it.
Orientation
Lattice reads a repo's issues, infers the dependency graph between them, stores it, and serves the resulting schedule to coding agents over MCP. It runs automatically — no approval step, no button. GitHub is a data source, not a data store: Lattice never writes to it.
| I'm working on… | Read |
|---|---|
| anything | AGENTS.md, docs/01-architecture.md |
| a GitHub API call | docs/09-github-api-notes.md — always, there are silent-failure traps |
| inference / prompts | docs/02-inference-pipeline.md |
| graph algorithms | docs/03-graph-scheduling.md |
| MCP tools | docs/04-mcp-surface.md |
| the store / caching | docs/11-graph-store.md |
| the REST API | docs/12-rest-api.md |
The rules that matter most
- Never write to GitHub. Reads only — no dependency writes, comments, labels or issue edits. And never bypass
validate.ts: there is no human review downstream, so those guards are the only check on what enters the graph. - Never weaken the DAG invariant in
src/graph/acyclic.tsto make something pass. - Never drop the
evidencefield or stop validating it against source text — an edge whose evidence can't be checked is an edge nobody can audit after the fact. - Respect the service boundary.
apps/webconsumes the REST API only — never the store, Octokit, or a model client. Extend the API instead of reaching around it. - Stay inside the
Scopelist in your issue body. Five people and several agents work this repo concurrently.
Build and test from the root: npm run build, npm test. Neither needs credentials.
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 · 38 lines · 654 tokens per session scan A a763a826b5df
lattice copilot-instructions.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 18d ago), licensed MIT. It adds 654 tokens to every session, about $0.0033 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
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.
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).
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).