Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add techygarg/lattice/plugin install 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/skills/techygarg/lattice/lattice-init)<a href="https://agentmods.dev/skills/techygarg/lattice/lattice-init"><img src="https://agentmods.dev/badge/skills/techygarg/lattice/lattice-init.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.1 | $0.00115 | $0.02991 |
| Opus 5 | $0.00057 | $0.01496 |
| Sonnet 5 | $0.00023 | $0.00598 |
| Haiku 4.5 | $0.00012 | $0.00299 |
Grade A, and why
lattice-init 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 7d 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lattice Init
Required Skills
Read apply skills order:
framework:knowledge-priming-- Load project context understand what project is what already exists
Workflow
Step 1: Scan the Project
Detect signals about project understand shape existing Lattice state.
Language/framework detection -- check files in repo root:
package.json→ Node.js / TypeScripttsconfig.json→ TypeScript (confirm over JavaScript)go.mod→ Gopom.xmlorbuild.gradleorbuild.gradle.kts→ Java or KotlinCargo.toml→ Rustrequirements.txtorpyproject.tomlorsetup.py→ PythonGemfile→ Ruby*.csprojor*.sln→ C# / .NETPackage.swift→ Swift
If multiple language markers are found in the repo root, note all of them and ask the user which is the primary stack before continuing.
Directory structure -- list top-level dirs. Identify common patterns:
src/,lib/,app/→ source codetest/,tests/,spec/→ test suitesdocs/→ documentationcmd/,internal/,pkg/→ Go project structuredomain/,infrastructure/,application/→ layered architecture
Existing .lattice/ state -- check what Lattice artifacts already exist:
.lattice/config.yaml→ central config (check forlanguagekey).lattice/standards/language-idioms.md→ language idioms refiner output.lattice/standards/knowledge-base.md→ knowledge priming output.lattice/standards/architecture.md→ architecture refiner output (clean architecture, hexagonal, modular monolith, or custom style).lattice/standards/clean-code.md→ clean code refiner output.lattice/standards/ddd-principles.md→ DDD refiner output.lattice/standards/review-standards.md→ review refiner output.lattice/context/→ feature context documents (count them).lattice/learnings/operational-learnings.md→ accumulated operational learnings (managed by learning-harvest atom).lattice/reviews/review-log.md→ review log.lattice/requirements/index.md→ check shape: if epic sections and feature tables are written directly inside it (noepics/directory alongside) andrequirements_layoutis absent from config, flag as legacy layout — upgrade available.lattice/verification.yaml→ verification stages config consumed by the verification runner.lattice/scripts/run-verification.sh→ vendored verification runner
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 171 lines · 115 tokens per session scan A b68921f0ac59
lattice-init is a skill published in the GitHub repository techygarg/lattice (185 stars, last pushed 2d ago), licensed MIT. It adds 115 tokens to every session and 2,991 once invoked, about $0.0006 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 skills, from other repositories
name-your-business
Generate, refine, compare, and when needed validate distinctive names for startups, AI products, developer tools, protocols, open-source projects, apps, product families, local businesses, services, companies, nonprofits, and other organizations. Use when asked to name or rename a business, brand, product, venture…
top-one-percent
Teach any topic deeply from first principles and build evidence-based paths toward exceptional capability. Use when a user asks to understand, explain, learn, or deep-dive into a topic; asks why or how something works, why it matters, how alternatives compare, or what different perspectives reveal; requests current…
paper-opportunity-radar
Run a cumulative daily or retrospective sweep of research papers on a chosen topic, audit their claims, methods, integrity signals, and independent support, then identify overlooked but feasible project or business opportunities in a detailed source-grounded report. Use when asked to monitor papers every day, mine…
repo-system-map
Analyze a software repository at the latest remote main commit and turn its implemented architecture into a citation-backed interactive isometric system map with a legend, selectable infrastructure buildings, dependency and payload flows, and plain-language learner explanations. For eligible public GitHub…
create-marketing-kit
Create truthful, human-centered marketing campaigns for an app or product, including positioning, channel copy, original artwork, editable layouts, README banners, and selective website integration. Use when asked to make launch materials, promotional artwork, social assets, campaign kits, ads, or marketing content…
run-smoke-tests
Inspect an unfamiliar repository, interpret a broad Markdown user journey at runtime, operate the real product through its supported web, API, CLI, desktop, or mobile surface, and produce an auditable pass, fail, or blocked judgment with screenshots, logs, recordings, and a step timeline when available. Use when asked…