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.00087 | $0.04989 |
| Opus 5.5 | $0.00035 | $0.01996 |
| Sonnet 5.5 | $0.00017 | $0.00998 |
| Haiku 4.5 | $0.00009 | $0.00499 |
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 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 — 480 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 loaders inside action buttons when scoped to that trigger.
- Place errors next to the thing that caused them unless the issue blocks the whole flow.
- Ensure every action gives visible or tactile feedback across all button states (default, hover, focus, pressed, loading, disabled; see Button States And Accessibility).
- Decide whether to keep submit enabled with focused error jump instead of disabled button traps.
- Make each page section resilient when other sections load slowly or fail.
- Apply Tesler's Law: absorb complexity in code and system design rather than offloading it to users.
- Use familiar patterns for the user's device, locale, and audience (Jakob's Law).
- Respect Fitts's Law: optimize tap target sizes, invisible hit padding, thumb reach, and resolve scroll-vs-tap gesture conflicts.
- Reduce choice overload with grouping, curation, filtering, or progressive disclosure without hiding core discoverability.
- Verify the final checklist at the bottom of this file.
What ships with it
1 file 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.
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 Changed · +128 lines · +37 tokens per session f0419e91c464
- 1mo 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 (16 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 87 tokens to every session and 4,989 once invoked, about $0.0003 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-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.
appllama-usage
Use the Appllama MCP (mcp.appllama.io) well — research real top-grossing mobile apps, their screens, flows, and UI elements, then build from what you learn. Load when the Appllama MCP is connected and the task involves building a mobile app or screen, researching app design patterns, studying…
appllama-app-design-skill
Build native-feeling, benchmark-quality mobile app screens (Expo / React Native). Use when designing or implementing any mobile UI — screens, flows, onboarding, paywalls, tab bars, sheets, settings, empty states — or when polishing motion, navigation, typography, dark mode, or perceived performance. Enforces Apple HIG…
excalidraw
Use when user requests diagrams, flowcharts, architecture charts, or visualizations. Also use proactively when explaining systems with 3+ components, complex data flows, or relationships that benefit from visual representation. Generates .excalidraw files and exports to PNG/SVG via Kroki API or locally using…
visual-brand-kit
Create visual identity systems for AI-generated content: colors, typography feel, photography style, composition rules, and prompt presets. Triggers on brand kits, visual guidelines, image style, and brand photography.
zhuangxiu-sheji-jiqiao-daquan
A Chinese reference guide to home renovation design, covering room layouts, movement paths, storage, styles, colours, and ways to avoid design mistakes.