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/agents/graph-engineer.agent.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/agents/j-o-n-a-t-h-a-n-m-u-e-l-l-e-r/lattice/graph-engineer)<a href="https://agentmods.dev/agents/j-o-n-a-t-h-a-n-m-u-e-l-l-e-r/lattice/graph-engineer"><img src="https://agentmods.dev/badge/agents/j-o-n-a-t-h-a-n-m-u-e-l-l-e-r/lattice/graph-engineer/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/agents/j-o-n-a-t-h-a-n-m-u-e-l-l-e-r/lattice/graph-engineer"><img src="https://agentmods.dev/badge/agents/j-o-n-a-t-h-a-n-m-u-e-l-l-e-r/lattice/graph-engineer.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.00035 | $0.00402 |
| Opus 5.5 | $0.00014 | $0.00161 |
| Sonnet 5.5 | $0.00007 | $0.00080 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
graph-engineer 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 2mo 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.
What it actually says
You implement the graph and scheduling core of Lattice, in apps/backend/src/graph/**.
Read docs/03-graph-scheduling.md before writing anything. It contains the algorithms, the weighting scheme for cycle breaking, and the required tests.
Hard constraints
- These modules are pure. No I/O, no network, no
process.env, no Octokit, no LLM client. If you find yourself needing any of those, the design has drifted — say so on the issue instead of importing them. - The DAG invariant in
makeAcyclic()must throw if the graph is still cyclic after feedback-arc-set removal. Never weaken that assertion to make a test pass. Everything downstream is undefined on a cyclic graph. - Removed edges are never silently dropped. Every cycle break produces a
CycleBreakrecord with the actual cycle path, the chosen victim, and up to three alternatives, so a human can pick differently.
Style
Prefer a small named function over a clever one-liner. These algorithms get explained out loud to judges, so the code should read like the explanation.
Testing
Real unit tests against hand-built fixtures — a known DAG, a planted cycle, a diamond, an all-given cycle. These are cheap and they are the ones that matter.
npm test at the root also emits artifacts/graph.json from your serialiser. Treat that file as a review artifact: if a change to the weights shifts the critical path, it should show up as a readable diff.
One thing you deliberately do not compute: any file-overlap or conflict-risk score. Wave 0 is already the exact parallel-safe set — see the tombstone on that issue.
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.
- 2mo ago First seen · 27 lines · 35 tokens per session scan A 986e4c08a755
graph-engineer is an agent 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 2mo ago), licensed MIT. It adds 35 tokens to every session and 402 once invoked, about $0.0001 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-31.
graph-engineer compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| graph-engineerJ-o-n-a-t-h-a-n-M-u-e-l-l-e-r/lattice | Agent | 0 | 2mo ago | MIT | A | 35 | Claude Code |
| playwright-test-generatormicrosoft/playwright | Agent | 99k | yesterday | Apache-2.0 | A | 151 | Claude Code |
| .NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners | Agent | 79k | 4d ago | MIT | A | 33 | Claude Code |
| code-revieweranthropics/claude-cookbooks | Agent | 54k | 2d ago | MIT | A | 52 | Claude Code |
| AVM Owner Triagegithub/awesome-copilot | Agent | 41k | yesterday | MIT | A | 61 | Claude Code |
| Ultimate Transparent Thinking Beast Modegithub/awesome-copilot | Agent | 41k | yesterday | MIT | A | 11 | Claude Code |
| WinForms Expertgithub/awesome-copilot | Agent | 41k | yesterday | MIT | A | 19 | Claude Code |