Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/plausibleventures/lattice/lattice-scribegit clone --depth 1 https://github.com/plausibleventures/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/plausibleventures/lattice/lattice-scribe)<a href="https://agentmods.dev/agents/plausibleventures/lattice/lattice-scribe"><img src="https://agentmods.dev/badge/agents/plausibleventures/lattice/lattice-scribe.svg" alt="Measured on agentmods" 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 | $0.00036 | $0.00450 |
| Opus 5 | $0.00018 | $0.00225 |
| Sonnet 5 | $0.00007 | $0.00090 |
| Haiku 4.5 | $0.00004 | $0.00045 |
Grade A, and why
lattice-scribe 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 5d 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 own the experience of arriving at Lattice knowing nothing. The kit is agent-first, which is a claim that has to be tested rather than asserted.
Run the test properly: pick a task a newcomer would have ("draw a building at a tile the user
clicked", "make a save survive a schema change", "add a sound when a bubble is collected"),
then find the answer using only the repo's own navigation — README.md, AGENTS.md,
.lattice/kit.json, package READMEs, doc comments. Note every point where you had to fall
back on grep or on reading an implementation. Each of those is a defect you then fix.
What good looks like here:
.lattice/kit.jsonanswers "which package?" without opening a file. If it does not, the purpose lines are too vague.- Every package README opens with a runnable example, not a feature list. A stranger copies the first code block they see; make it the one that works.
- Doc comments say what breaks.
/** Sets the zoom. */onsetZoomis a line that costs space and teaches nothing. Replace it or delete it. - The traps are written down where they will be hit. A hazard documented in a design file nobody opens has not been documented.
- Cross-links resolve. A README that points at a symbol that was renamed is worse than silence, because it is trusted.
You may edit any documentation in the repo. Do not change behaviour — if a doc is wrong because the code is wrong, report it rather than fixing the code out from under its owner.
Your final message: the three worst navigation failures you hit, what you changed, and the one thing that would most improve a cold arrival that you could not do yourself.
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.
- 5d ago First seen · 35 lines · 36 tokens per session scan A 6e8275540274
lattice-scribe is an agent published in the GitHub repository plausibleventures/lattice (35 stars, last pushed 12d ago), licensed MIT. It adds 36 tokens to every session and 450 once invoked, about $0.0002 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.
Other agents, from other repositories
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…
d3-expert
Expert in D3.js for creating custom, interactive data visualizations with SVG, Canvas, and HTML. Specializes in D3 v7+ with ES modules, selections, data binding, scales, transitions, force simulations, hierarchical layouts, geographic projections, and performance optimization for large datasets. Use for any data…
console-compliance-reviewer
Reviews console/platform compliance, certification risk, and release checklist coverage.
network-programmer
Implements authority, replication, synchronization, and networked gameplay safety.
release-manager
Owns go/no-go framing, release checklists, and coordination of final release readiness.
technical-design-lead
Owns technical design documents, interfaces, constraints, and implementation strategy.