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 LerianStudio/ring --skill validating-ux-completenessgit clone --depth 1 https://github.com/LerianStudio/ringWrote 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/lerianstudio/ring/validating-ux-completeness)<a href="https://agentmods.dev/skills/lerianstudio/ring/validating-ux-completeness"><img src="https://agentmods.dev/badge/skills/lerianstudio/ring/validating-ux-completeness/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/lerianstudio/ring/validating-ux-completeness"><img src="https://agentmods.dev/badge/skills/lerianstudio/ring/validating-ux-completeness.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.00113 | $0.01305 |
| Opus 5.5 | $0.00045 | $0.00522 |
| Sonnet 5.5 | $0.00023 | $0.00261 |
| Haiku 4.5 | $0.00011 | $0.00130 |
Grade A, and why
ring:validating-ux-completeness 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 1mo 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX Completeness Validation
Standalone utility — not a gate in any pre-dev track. Verifies that UX specifications are COMPLETE before investing in technical architecture. This is a VALIDATION pass — it checks existing artifacts, does not create new ones.
The TRD does not hard-block on this verdict: ring:writing-trds honors design-validation.md if present; if absent, it proceeds and notes the UX risk.
When to use
- Feature has UI and a standalone product-designer run produced UX artifacts
- Before starting the TRD (recommended slot: between PRD and TRD)
- The pre-dev orchestrators recommend it as an optional standalone step when the feature has UI
- User asks to "validate design" or "check if design is complete"
Skip when
- Feature is backend-only with no UI
- Pure API/infrastructure task
- Bug fix with no UX changes
Sequence
Runs before: ring:writing-trds (recommended, not required) Runs after: ring:writing-prds and a standalone product-designer run (ux-validation mode; optionally ux-design mode)
Entry Criteria
| Artifact | Location | Required |
|---|---|---|
prd.md |
docs/pre-dev/{feature}/ |
always |
ux-criteria.md |
docs/pre-dev/{feature}/ |
yes — produced by product-designer ux-validation mode |
wireframes/ |
docs/pre-dev/{feature}/wireframes/ |
yes — produced by product-designer ux-validation mode |
user-flows.md |
docs/pre-dev/{feature}/ |
only if a ux-design run happened — do NOT require otherwise |
If prd.md, ux-criteria.md, or wireframes/ are missing → STOP. Report the missing artifacts and recommend a product-designer run first.
If feature has NO UI → this skill does not apply. Feature has UI if PRD contains: user stories with "see", "view", "click", "navigate", "page", "screen", "button", "form", or features involving login, dashboard, settings, profile, reports, notifications.
Validation Checklist
Section 1: Screen Completeness (CRITICAL — failure = NEEDS REVISION)
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.
- 1mo ago First seen · 139 lines · 113 tokens per session scan A ae5184540eb5
ring:validating-ux-completeness is a skill published in the GitHub repository LerianStudio/ring (218 stars, last pushed 7d ago), licensed Apache-2.0. It adds 113 tokens to every session and 1,305 once invoked, about $0.0005 per session on Opus 5.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 skills, from other repositories
a11y-audit
Dedicated WCAG 2.2 AA/AAA accessibility audit across 10 dimensions (A1-A10) covering semantic HTML, keyboard navigation, ARIA patterns, color contrast, forms, images/media, responsive/zoom, motion/animation, reading/content, and legal compliance. Goes far beyond surface-level design-review checks with deep…
design-review
UI/UX design consistency audit. Code-based DX1-DX20 checklist covering states, consistency, accessibility, responsive behavior, and interaction patterns. Optional visual audit via chrome-devtools screenshots and automated WCAG accessibility via axe-core. DAP1-DAP12 anti-pattern detection. Modes: [path], visual…
design
Intent-first UI design with conscious, traceable design decisions. Persists decisions in .interface-design/ for cross-session consistency. Includes domain exploration, design system generation (system.md + system.json), per-component construction with mandatory checkpoints, and craft validation tests. Modes: init…
ui-design-team
Multi-agent UI review with 4 specialist perspectives: UX Researcher, Visual Designer, i18n/Multilingual QA, and Accessibility/Performance Auditor. Each agent scores independently from their expertise. Lead Designer synthesizes into prioritized fixes with exact code. Works with any stack: React, Astro, vanilla…
ux-ui
Use this agent when you need to design, audit, migrate, rewire, or rewrite UX/UI.
plain-language-ui
Use this agent whenever building, adding, or redesigning any screen, form, page, dashboard, wizard, table, or component in a compliance/fintech/regtech app (AML, KYC, VAT, payroll, audit, CSSF, tax filing), whenever the user says labels are cryptic or confusing ("I don't understand this button/field"), or whenever…