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 alper-dev/build-for-good-ux-skill --skill build-for-good-ux-skillgit clone --depth 1 https://github.com/alper-dev/build-for-good-ux-skillWrote 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/alper-dev/build-for-good-ux-skill/build-for-good-ux-skill)<a href="https://agentmods.dev/skills/alper-dev/build-for-good-ux-skill/build-for-good-ux-skill"><img src="https://agentmods.dev/badge/skills/alper-dev/build-for-good-ux-skill/build-for-good-ux-skill/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/alper-dev/build-for-good-ux-skill/build-for-good-ux-skill"><img src="https://agentmods.dev/badge/skills/alper-dev/build-for-good-ux-skill/build-for-good-ux-skill.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.00050 | $0.03033 |
| Opus 5 | $0.00025 | $0.01517 |
| Sonnet 5 | $0.00010 | $0.00607 |
| Haiku 4.5 | $0.00005 | $0.00303 |
Grade A, and why
build-for-good-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 — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build For Good UX
Based on Katherine Gilligan's public "Build For Good UX" series (@synsation_). Use this as an implementation checklist for UI work, not as transcript notes.
Core Principle
Good UI is how an app looks. Good UX is whether users understand what to do, what happened, what failed, and how to recover. AI-generated UI often covers only the happy path. Build the full experience.
Every screen needs these states:
| State | Required UX |
|---|---|
| Loading | Shows progress appropriate to wait time and scope |
| Success | Confirms the user's action worked |
| Error | Explains what happened, why, and next action |
| Empty | Explains why nothing is there and how to start or continue |
Good UX builds trust. Bad UX creates uncertainty, extra steps, and friction. Users leave and blame the product, not themselves.
Required Workflow
When building or reviewing a UI, do this before considering the work complete:
- Identify every user action and async data source.
- Define loading, success, error, and empty states for each relevant screen or section.
- Pick the loader based on scope and duration.
- Place errors next to the thing that caused them unless the issue blocks the whole flow.
- Ensure every action gives visible feedback.
- Make each page section resilient when other sections load slowly or fail.
- Use familiar patterns for the user's device, locale, and audience.
- Reduce choice overload with grouping, curation, filtering, or progressive disclosure.
- Verify the final checklist at the bottom of this file.
Loading States
Missing loaders make users think the app is broken. A blank screen with no response can lose users in 2-3 seconds. Bad loaders can also make the app feel slower.
Choose Loader By Context
| Pattern | Use When | Avoid When |
|---|---|---|
| Skeleton screen | Whole page or large content section loads | Small contained action |
| Progress bar | Duration or progress is knowable | Unknown background wait |
| Inline spinner | Button or small section is working | Whole page load |
| Optimistic UI | Action is very likely to succeed | Failure would be costly or confusing |
| No loader | Work finishes under 1 second | Delay may exceed 1 second |
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 · 352 lines · 50 tokens per session scan A 23f29b6d36aa
build-for-good-ux is a skill published in the GitHub repository alper-dev/build-for-good-ux-skill (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 50 tokens to every session and 3,033 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-30.
Other skills, from other repositories
page-flow-cleanup-audit
A review process for cleaning up a user-facing page or feature flow by tracing where its data and states come from. It checks loading, empty, error, permission, and lifecycle behavior before removing unnecessary code.
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Covers design thinking, typography pairing, color theory, motion design, spatial composition, and code quality. Generates real working code — HTML/CSS/JS or React — with intentional aesthetic direction, not generic AI output.
better-ui
Polishes and improves the UI in your project. Covers concentric border radius, optical alignment, surface depth, contextual icons, hit areas and more.
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
web-design-director
Skill "web-design-director" from guia-matthieu/clawfu-skills, covering web design director, when to use this skill, methodology foundation, what claude does vs what you decide and what this skill does.
website-finishing-director
Run a structured 5-pass finishing audit on any website before launch — scoring visual polish, technical foundation, UX completeness, content quality, and cross-device readiness on 100 points. Use when: Pre-launch - Final validation before going live; Post-redesign - Verify nothing broke during the overhaul; Client…