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 instructions/techygarg/lattice/claude-mdgit clone --depth 1 https://github.com/techygarg/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/techygarg/lattice/claude-md)<a href="https://agentmods.dev/instructions/techygarg/lattice/claude-md"><img src="https://agentmods.dev/badge/instructions/techygarg/lattice/claude-md.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.00056 | $0.00056 |
| Opus 5 | $0.00028 | $0.00028 |
| Sonnet 5 | $0.00011 | $0.00011 |
| Haiku 4.5 | $0.00006 | $0.00006 |
Grade A, and why
lattice CLAUDE.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 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
Lattice — Claude Code
Read and follow PROJECT.md in this repository. All Lattice conventions, structure, skill rules, patterns, and anti-patterns live there. This file exists so Claude Code loads project context from the repo root.
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 · 4 lines · 56 tokens per session scan A 17ff09b0909d
lattice CLAUDE.md is an instructions file published in the GitHub repository techygarg/lattice (183 stars, last pushed 6d ago), licensed MIT. It adds 56 tokens to every session, about $0.0003 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 instructions, from other repositories
forge CLAUDE.md
Claude Code instructions for TT-Wang/forge, covering forge, quick start, skills, agents and mcp tools.
builder-essential-skills AGENTS.md
Instructions for tamdogood/builder-essential-skills, covering agent notes and cinematic banner typography.
litestar-skills AGENTS.md
Instructions for litestar-org/litestar-skills, covering litestar-skills agent context, mission, agent conduct, skill authoring rules and supported hosts.
cc-notify-hooks CLAUDE.md
Instructions for MarioZZJ/cc-notify-hooks, covering cc-notify-hooks, 技术栈, 项目结构, 常用命令 and 安装.
claude-proj-blueprint CLAUDE.md
Claude Code instructions for maduwanthasathsara0-hub/claude-proj-blueprint, covering project, tech stack, architecture, documentation directories and code conventions.
virtual-company CLAUDE.md
Instructions for k1lgor/virtual-company, covering 🏢 virtual company: claude code plugin, 🛑 the iron law, 📢 completion status protocol, 🧠 operational self-improvement (learning log) and 📜 core operating principles.