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 skills add techygarg/lattice --skill architecture-compassgit 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/skills/techygarg/lattice/architecture-compass)<a href="https://agentmods.dev/skills/techygarg/lattice/architecture-compass"><img src="https://agentmods.dev/badge/skills/techygarg/lattice/architecture-compass.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00114 | $0.03781 |
| Opus 5 | $0.00057 | $0.01891 |
| Sonnet 5 | $0.00023 | $0.00756 |
| Haiku 4.5 | $0.00011 | $0.00378 |
Grade A, and why
architecture-compass 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 8d 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Compass
Required Skills
Read, apply:
framework:knowledge-priming-- Load codebase context: language, framework, structure, conventions (always)framework:architecture-- Architectural audit lens and recommended direction guardrails (always)framework:domain-driven-design-- Strategic DDD only: bounded contexts, domain seams (conditional: only when domain complexity warrants it)framework:collaborative-judgment-- Surface judgment calls during co-design rounds (always)
Workflow
Step 1: Load Existing Context
Check for an existing insights document first. If .lattice/insights/architecture.md already exists:
- Read it. Check the Session Status table using these three states:
pending— row exists, no content written yetin-progress— content exists in the section but no agreed date recorded✅ agreed— content exists and date is recorded
- Resume from the earliest
pendingorin-progressphase. Forin-progressphases: present the existing content for re-confirmation rather than regenerating it. - In-progress without content: If Current Architecture is
in-progressbut the document has no Current Architecture content (the previous session's scan context was lost), re-run Step 2 scan before presenting. - Staleness check: If the most recent
✅ agreeddate in the Session Status table is older than 30 days, run a lightweight re-scan (Steps 2.1 and 2.6 only — tree + imports). If material structural changes are detected, present them and ask whether Current Architecture needs revision before proceeding. - Do not re-scan if Current Architecture is already
✅ agreedand the staleness check passes. - Tell the user what was found and which phase the session resumes from.
If no existing document: proceed from Step 2.
Check for .lattice/config.yaml. Load knowledge-base.md and architecture.md from .lattice/standards/ if they exist — these shape both the audit lens and the recommended direction proposal.
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.
- 8d ago First seen · 277 lines · 114 tokens per session scan A 8bddcca171cf
architecture-compass is a skill published in the GitHub repository techygarg/lattice (185 stars, last pushed today), licensed MIT. It adds 114 tokens to every session and 3,781 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
code-standards
Apply a disciplined engineering workflow to any code change. Use whenever implementing a feature, fixing a bug, or refactoring — before writing code, not after. Walks orient → baseline → smallest change → test → verify → self-review, and enforces language-agnostic hard gates (don't mass-reformat, keep the linter and…
gaia-issue-resolver
End-to-end plan → implement → review pipeline that takes one triaged Gaia issue to a merged-ready PR, with Kill Criteria on the issue and zero follow-up debt. Use when someone says: "resolve this issue", "take #N end-to-end", "work the P0 queue", "fix and ship this issue", "run the resolver", "close out this issue…
gemini
Cross-model second opinion from Google Gemini — a different AI reviewing the same changes, with deep Google ecosystem knowledge. Three modes: review (pass/fail gate for Google Ads campaigns, SEO metadata, or code), challenge (adversarial stress-test that tries to break your changes), and consult (open Q&A with Gemini…
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
boundaries
Analyze Phoenix context boundaries and module coupling via mix xref. Use when checking cross-context calls, validating dependencies, before splitting modules, or reviewing architecture.
triage
Triage review findings interactively — approve, skip, or prioritize each issue. Use after /phx:review to filter findings before fixing.