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 language-idioms-refinergit 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/language-idioms-refiner)<a href="https://agentmods.dev/skills/techygarg/lattice/language-idioms-refiner"><img src="https://agentmods.dev/badge/skills/techygarg/lattice/language-idioms-refiner/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/techygarg/lattice/language-idioms-refiner"><img src="https://agentmods.dev/badge/skills/techygarg/lattice/language-idioms-refiner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 78 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00092 | $0.03788 |
| Opus 5 | $0.00046 | $0.01894 |
| Sonnet 5 | $0.00018 | $0.00758 |
| Haiku 4.5 | $0.00009 | $0.00379 |
Grade A, and why
language-idioms-refiner 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 10d 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Language Idioms Refiner
What This Produces
- Output:
.lattice/standards/language-idioms.md(or custom path from.lattice/config.yaml->paths.language_idioms) - Mode: Always standalone -- no embedded language defaults exist in atoms to overlay on. For revisions, load existing document and update sections in place.
- Config keys:
language(top-level) -- language identifier (e.g.,go,rust,python,java,typescript)paths.language_idioms-- path to the produced document
- Template: Read
./assets/template.mdfor the full document structure, pre-populated examples, and interview guidance comments - Consumed by: Multiple atoms reference specific sections by heading name:
| Section | Consumed by |
|---|---|
| Error Handling | clean-code atom (§8), secure-coding atom (§2 validation error messages) |
| Type System & Object Model | clean-code atom (§1 SRP/cohesion), domain-driven-design atom (entities, VOs, aggregates) |
| Naming Conventions | clean-code atom (§4) |
| Testing Patterns | test-quality atom (§5 naming, §4 isolation, §6 builders) |
| Parameter & Function Design | clean-code atom (§2 function size, §5 parameters) |
| Dependency Management | clean-code atom (§9 testability/DI), architecture atom (dependency direction) |
These six section headings are the stable contract. Atoms reference them by name. Additional sections can be added by consumers but these six must be present.
Scope Clarification
This document captures how the project's language expresses engineering patterns -- the language-level idioms that atoms need to adapt their pseudocode defaults. Clear boundaries:
| Concern | Where It Belongs | Not Here |
|---|---|---|
| Project identity, tech stack, directory layout | knowledge-priming atom |
No project structure or framework docs |
| Code craftsmanship rules (thresholds, heuristics) | clean-code atom / overlay |
No function size limits or DRY rules |
| Architecture layers, dependency direction | architecture atom / overlay |
No layer definitions |
| Domain modeling guardrails | domain-driven-design atom / overlay |
No aggregate rules |
| Team-specific preferences within language | Atom-specific overlays | No team decisions (see below) |
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.
- 10d ago First seen · 249 lines · 92 tokens per session scan A db2349f02a10
language-idioms-refiner is a skill published in the GitHub repository techygarg/lattice (186 stars, last pushed 2d ago), licensed MIT. It adds 92 tokens to every session and 3,788 once invoked, about $0.0005 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
phx-deps-audit
Audit Hex deps for supply-chain security risk — bidi chars, compile-time exec, maintainer changes, typosquats, CVEs. Use after mix deps.update, when checking if a package upgrade is safe, or reviewing mix.lock PR diffs.
deps-update
Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo). Use to upgrade/bump Elixir dependencies or when versions fall behind. NOT for deps.get failures (/phx:investigate).
deps-vet
Record a vetted Hex package version in hexvet.exs after a security review — manages the audit ledger, not the scanner. Use to approve a dep after /phx:deps-audit findings or to initialize hexvet.exs.
phx-plan
Plan features spanning multiple domains: billing (Stripe), auth (RBAC), real-time (Presence), webhooks, jobs (Oban). Use when designing interconnected systems or converting review findings into tasks.
phx-deps-update
Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo). Use to upgrade/bump Elixir dependencies or when versions fall behind. NOT for deps.get failures (phx-investigate).
phx-full
Run a portable sequential plan-work-verify-review-compound lifecycle. Use optional generic workers only when Amp makes them available.