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 aryaniyaps/lamina --skill lamina-uxgit clone --depth 1 https://github.com/aryaniyaps/laminaWrote 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/aryaniyaps/lamina/lamina-ux)<a href="https://agentmods.dev/skills/aryaniyaps/lamina/lamina-ux"><img src="https://agentmods.dev/badge/skills/aryaniyaps/lamina/lamina-ux/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/aryaniyaps/lamina/lamina-ux"><img src="https://agentmods.dev/badge/skills/aryaniyaps/lamina/lamina-ux.svg" alt="Reviewed on agentmods" width="80" 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.00079 | $0.00812 |
| Opus 5 | $0.00039 | $0.00406 |
| Sonnet 5 | $0.00016 | $0.00162 |
| Haiku 4.5 | $0.00008 | $0.00081 |
Grade A, and why
lamina-ux 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 11d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lamina UX
Reference-loading protocol
- Match the request's primary interaction risk to one row below.
- Open that linked reference before answering. Add another only when a second risk materially changes the answer; do not preload the directory.
- Start the response with
Using lamina-ux: <topic path(s)>so the selected interaction lens is auditable.
Topic index
| Interaction signal | Read | Adds |
|---|---|---|
| Need the end-to-end design-to-implementation loop | Design Process | Persona walks, graph expansion, implementation, and verification lifecycle |
| Need to order steps, branches, prerequisites, and recovery for one outcome | Workflow Design | operation-level flow structure |
| Need to group product concepts, hierarchy, labels, or findability | Information Architecture | entity- and task-based organization |
| Users are lost between destinations or cannot maintain orientation | Navigation | wayfinding, current location, and route structure |
| Need labels, headings, instructions, empty copy, or error copy | Content Design | consistent, scan-first interface language |
| Need input semantics, validation timing, field errors, or submission recovery | Forms | accessible validation and data-entry behavior |
| Need action hierarchy, destructive-action policy, menus, confirmation, or undo | Controls and Actions | explicit action semantics and reversibility |
| A collection or account has no data yet | Empty States | scenario-bound explanation and next action |
| New or returning users cannot reach first value | Onboarding | minimal setup, permissions, and resumable progress |
| Users cannot tell whether an action started, succeeded, failed, or is delayed | Feedback and Status | visible transient and terminal states |
| Need actor-visible failure language and a concrete recovery path | Error Handling | error categories, recovery, and blame-free copy |
| The interface exposes too much complexity at once | Progressive Disclosure | essential versus advanced action tiers |
| Users cannot perceive an available action or its consequence | Discoverability | signifiers, disabled reasons, and feedback gulfs |
| Need keyboard, screen-reader, focus, announcement, contrast, or touch behavior | Accessibility | interaction-specific accessible acceptance criteria |
| Behavior changes through invitations, persuasion, groups, or social influence | Multi-Actor Dynamics | consent, autonomy, and group-effect safeguards |
| A high-stakes action needs honest consequence, fee, privacy, or success signals | Trust Signals | observable product honesty |
| Need distinct denied, stale, concurrent, destructive, or dependency-failure cases | Distinct Product Risks | non-duplicative scenarios with observable acceptance |
What ships with it
17 files 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.
- references/accessibility.md 695 B
- references/content-design.md 1.6 KB
- references/controls-and-menus.md 1.6 KB
- references/design-process.md 1.6 KB
- references/discoverability.md 1.4 KB
- references/edge-cases.md 914 B
- references/empty-states.md 1.1 KB
- references/error-handling.md 1.4 KB
- references/feedback-and-status.md 1.5 KB
- references/flow-design.md 752 B
- references/forms.md 2.8 KB
- references/information-architecture.md 1.4 KB
- references/navigation.md 1.2 KB
- references/onboarding.md 1.5 KB
- references/persuasion-and-groups.md 602 B
- references/progressive-disclosure.md 1.2 KB
- references/trust.md 1.9 KB
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.
- 11d ago First seen · 45 lines · 79 tokens per session scan A 0862439ad736
lamina-ux is a skill published in the GitHub repository aryaniyaps/lamina (114 stars, last pushed today), licensed Apache-2.0. It adds 79 tokens to every session and 812 once invoked, about $0.0004 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
ppt-orchestrator
A dispatcher for creating presentations, slide decks, long images, and weekly reports. It chooses a visual style and output format, then sends the work to a more specialised add-on.
zhongguose-html-skill
An HTML-only presentation system using traditional Chinese colours and Chinese-style visual design. It helps organise source material into a report structure and produces a self-contained HTML file with its assets.
pneuma-preferences
Persistent user preference memory across sessions. Consult this skill BEFORE making any design, style, or aesthetic decisions — choosing colors, themes, layouts, fonts, tone of voice, content density, or visual direction. Also consult when starting a new creative task in any mode, when the user corrects your style…
design-swarm
Orchestrate a team of 10 design agents for holistic UI audit, ideation, and implementation. Use when: "design swarm", "holistic audit", "design review with all lenses", "full design analysis". Modes: audit, ideate, implement (any combination). Targets: screenshots, URLs, file paths, or text briefs.
FlowForge
A draw.io diagram tool that turns a description or document into editable visual diagrams. Draw.io is software for making flowcharts, system diagrams, and other structured illustrations.
ui-ux-design
Create production-grade frontend interfaces with strong UX and visual craft. Use when building web components, pages, dashboards, forms, landing pages, modals, or any UI. Use when user says 'build a form', 'create a dashboard', 'design a component', 'make a landing page', or asks for UI/UX work. Use even when the user…