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 skills/techygarg/lattice/skill-alignnpx skills add techygarg/lattice --skill skill-aligngit 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/skill-align)<a href="https://agentmods.dev/skills/techygarg/lattice/skill-align"><img src="https://agentmods.dev/badge/skills/techygarg/lattice/skill-align.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.00160 | $0.01945 |
| Opus 5 | $0.00080 | $0.00972 |
| Sonnet 5 | $0.00032 | $0.00389 |
| Haiku 4.5 | $0.00016 | $0.00194 |
Grade A, and why
skill-align 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 3d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lattice Sync
Core responsibility: Keep every public-facing document in sync with the actual skill inventory. The skills directory is the source of truth — all documents derive from it.
Input: None required. Reads the live state of skills/ and all documentation on every run. Optionally: a specific skill name or tier to focus the audit.
Output:
- A findings report listing every gap as
[GAP],[STALE], or[WRONG]with file and description - All found gaps fixed in-place across:
README.md,docs/how-it-works.md,docs/configuration.md,docs/practical-guide.md,PROJECT.md,CLAUDE.md,.github/ISSUE_TEMPLATE/bug_report.yml - A final clean confirmation: "No gaps found" or a list of what was changed
How to verify this skill did its job:
grep -rn "requirements atom\|framework:requirements\b" \
docs/ README.md PROJECT.md CLAUDE.md .github/ skills/ \
--include="*.md" --include="*.yml"
Any result from this grep means the sync is incomplete. A clean run returns no output.
Also verify: every skill in skills/ appears in the bug_report.yml dropdown and the how-it-works.md inventory tables.
When to run
- After creating any new atom, molecule, or refiner
- After renaming or removing a skill
- After changing a skill's config key, consumed-by relationships, or output path
- When a user suspects docs are out of date
Phase 1 — Build the live inventory
Read the skills directory tree. STOP: do NOT assume you already know the inventory — always read from files.
find skills/ -name "SKILL.md" | sort
For each SKILL.md found, extract:
name:field (frontmatter)tier:inferred from path (atoms/,molecules/,refiners/)- Config key: grep for
paths\.\w+in the file - Consumes: grep for
framework:references (molecules only) - Produces: grep for
.lattice/standards/path (refiners only) - Output subfolder: grep for
.lattice/\w+/paths (molecules only)
Build a structured inventory:
atoms: [name, config_key, has_refiner, has_defaults_md]
molecules: [name, composes[], output_subfolder]
refiners: [name, config_key, produces_path, consumed_by_atom]
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.
- 3d ago First seen · 170 lines · 160 tokens per session scan A d5d5e40e5d6b
skill-align is a skill published in the GitHub repository techygarg/lattice (183 stars, last pushed 5d ago), licensed MIT. It adds 160 tokens to every session and 1,945 once invoked, about $0.0008 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
xiaoyaoclaw-workspace-initializer
OpenClaw workspace initialization & standardization. Sets up a proper agent home: standard directory structure (projects/tasks/outputs/knowledge/scripts/ memory/tmp) + WORKSPACE.md rules + multi-agent config safety (config.patch, never config.apply) + memory log. Use when an agent enters a new/empty workspace root, or…
learn
Search, install, update, and rate AI agent skills from agentskill.sh (100,000+ skills). Use when the user asks to find skills, install extensions or plugins, discover new capabilities, check what skills are available, or says "how do I do X" when a skill might help. Also handles listing installed skills, checking for…
review-skill
Review and improve AI agent skills (SKILL.md files) against best practices from the Agent Skills specification and Anthropic's authoring guidelines. Scores skills on 10 quality dimensions, identifies specific issues, and rewrites problem areas. Use when creating, editing, auditing, or improving agent skills. Triggers…
building-chatgpt-apps
Guides creation of ChatGPT Apps with interactive widgets using OpenAI Apps SDK and MCP servers. Use when building ChatGPT custom apps with visual UI components, embedded widgets, or rich interactive experiences. Covers widget architecture, MCP server setup with FastMCP, response metadata, and Developer Mode…
memory-systems
Design and implement memory architectures for agent systems. Use when building agents that need to persist state across sessions, maintain entity consistency, or reason over structured knowledge.
multi-agent-patterns
Design multi-agent architectures for complex tasks. Use when single-agent context limits are exceeded, when tasks decompose naturally into subtasks, or when specializing agents improves quality.