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 ASMN-96/ai-agents-skills-toolkit --skill uiuxgit clone --depth 1 https://github.com/ASMN-96/ai-agents-skills-toolkitWrote 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/asmn-96/ai-agents-skills-toolkit/uiux)<a href="https://agentmods.dev/skills/asmn-96/ai-agents-skills-toolkit/uiux"><img src="https://agentmods.dev/badge/skills/asmn-96/ai-agents-skills-toolkit/uiux/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/asmn-96/ai-agents-skills-toolkit/uiux"><img src="https://agentmods.dev/badge/skills/asmn-96/ai-agents-skills-toolkit/uiux.svg" alt="Reviewed on agentmods" width="80" 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.00056 | $0.00656 |
| Opus 5 | $0.00028 | $0.00328 |
| Sonnet 5 | $0.00011 | $0.00131 |
| Haiku 4.5 | $0.00006 | $0.00066 |
Grade A, and why
uiux 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UIUX
Use this as the canonical final UI/UX authority skill for frontend, dashboard, wizard, app, and browser-visible experiences.
This skill produces UX critique, design intent, acceptance criteria, and implementation handoff. It does not authorize package changes, framework changes, CI edits, MCP setup, global config changes, backend/security changes, external design-source activation, or claims of browser verification without observed evidence.
Review Focus
- Primary workflow clarity, user intent, and product value.
- Responsive layout, mobile behavior, accessibility, keyboard usability, and safe interaction states.
- Visual hierarchy, spacing, density, typography, motion, empty/error/loading states, and text fit.
- Design-system constraints, local project source of truth, and consistency across repeated components.
- Dashboard, chart, form, navigation, and data UI acceptance criteria when relevant.
- Evidence quality: screenshots, browser checks, or manual QA must be labeled honestly.
Measurable UX Targets
- Accessibility claims should target WCAG 2.1 AA and keyboard reachability unless the project sets a stricter standard.
- Lighthouse performance, accessibility, best-practice, or SEO scores count only when Lighthouse actually runs against the relevant page or build.
- Browser-visible layout claims need evidence for the smallest relevant mobile width and one desktop width, or a clear reason the check could not run.
- Do not claim pixel-perfect, accessible, responsive, or production-ready UI from design intent, screenshots alone, or registry metadata.
Source Boundaries
Use normalized guidance from reviewed UI/UX source maps and methods only. Do not activate open-design, UI UX Pro Max, shadcn CLI/MCP, external design scripts, raw prompts, registry JSON, component source, blocks, package config, or unmanaged design-system files.
For v0.2 project tooling, use .ai-toolkit/docs/UIUX_DESIGN_RESOURCES.md for design-resource boundaries and .ai-toolkit/methods/mobile/native-mobile-app-quality.md for mobile quality routing. Canonical toolkit sources: docs/UIUX_DESIGN_RESOURCES.md and methods/mobile/native-mobile-app-quality.md. Base UI and Figma are excluded from current-scope recommendations.
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 · 43 lines · 56 tokens per session scan A 32a494ce84cb
uiux is a skill published in the GitHub repository ASMN-96/ai-agents-skills-toolkit (5 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 656 once invoked, about $0.0003 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-31.
Other skills, from other repositories
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
taiyi-diagram-arch
A workflow for turning written system or product architecture into readable, version-controlled diagrams using Mermaid or exported SVG and PNG files. Architecture diagrams show components, boundaries, data flows, and deployment relationships.
taiyi-restyle
A planning guide for breaking a large user-interface redesign into smaller, independently reviewable tasks. A user interface is the part of an application that people see and use.
taiyi-diagram-pipeline
A pipeline that creates and updates architecture diagrams in three stages: a C4 model from the code, an engineering architecture diagram, and an exported PNG image. C4 is a way to describe software architecture at several levels of detail.
taiyi-diagram-render
A tool for rendering existing C4 or architecture Mermaid diagrams as SVG or PNG images. C4 is a way to show software systems at different levels, while Mermaid is a text format for diagrams.
flowchart-creator
Create HTML flowcharts and process diagrams with decision trees, color-coded stages, arrows, and swimlanes. Use when users request flowcharts, process diagrams, workflow visualizations, or decision trees.