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.
git clone --depth 1 https://github.com/HermeticOrmus/LibreUIUX-Claude-CodeWrote 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/commands/hermeticormus/libreuiux-claude-code/design-audit)<a href="https://agentmods.dev/commands/hermeticormus/libreuiux-claude-code/design-audit"><img src="https://agentmods.dev/badge/commands/hermeticormus/libreuiux-claude-code/design-audit.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.00025 | $0.01525 |
| Opus 5 | $0.00013 | $0.00763 |
| Sonnet 5 | $0.00005 | $0.00305 |
| Haiku 4.5 | $0.00003 | $0.00153 |
Grade A, and why
design-audit 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 5d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- design-audit — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design Audit Command
You are conducting a comprehensive design audit of the provided design, component, or interface.
Audit Framework
Evaluate across these dimensions, scoring 1-10 and providing specific feedback:
1. Visual Hierarchy (Weight: High)
Check:
- Clear focal point - eye knows where to go first
- Logical reading order - F-pattern or Z-pattern flow
- Appropriate scale relationships - importance reflected in size
- Contrast creates emphasis - color, weight, space differentiation
- Progressive disclosure - complexity revealed appropriately
Questions to Ask:
- Can a user identify the primary action in under 3 seconds?
- Is there a clear path from most to least important elements?
- Does anything compete inappropriately for attention?
2. Typography (Weight: High)
Check:
- Limited typeface palette - 2-3 fonts maximum
- Clear hierarchy - display, heading, body, caption distinct
- Readable body text - 45-75 characters per line
- Appropriate line height - 1.5 for body, 1.2 for headings
- Consistent scale - following a mathematical ratio
Questions to Ask:
- Is there a clear typographic system?
- Can you identify heading levels without seeing code?
- Is body text comfortable to read in long form?
3. Color Usage (Weight: High)
Check:
- Limited palette - primary, secondary, accent, neutrals
- 60-30-10 proportions - or intentional variation
- Semantic consistency - same colors mean same things
- Accessibility - WCAG AA contrast ratios
- Emotional alignment - colors match brand personality
Questions to Ask:
- Does the color palette tell a consistent story?
- Can colorblind users navigate effectively?
- Are there any contrast failures?
4. Spacing & Layout (Weight: High)
Check:
- Consistent spacing scale - 4px/8px base or similar
- Sufficient white space - elements have room to breathe
- Logical grouping - related items are proximate
- Grid adherence - or intentional deviation
- Responsive consideration - scaling makes sense
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.
- 5d ago First seen · 214 lines · 25 tokens per session scan A f5b5dc1b510f
design-audit is a command published in the GitHub repository HermeticOrmus/LibreUIUX-Claude-Code (101 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 1,525 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
design-qa
Agent-driven design QA — walk the running app, judge design/UX, and drop a Comment-Mode comment on every issue (visible to the human as pins). Then read the session back and fix everything in bulk. Optional focus argument steers the pass.
excalidraw
Create or modify an editable Excalidraw diagram.
diagram-coordinator
Coordinate with agents to generate comprehensive educational diagrams.
diagram-from-file
Generate educational diagram from a source file using Excalidraw.
design-audit
Systematic evaluation of existing designs against fundamental principles. Provides actionable feedback rooted in design theory and best practices.
brand-identity
Guided workflow for creating comprehensive brand identity systems. Walks through discovery, strategy, visual identity, and guidelines creation.