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 agentmods add skills/pilot617/awesome-claude-code-plugins/ui-ux-buildernpx skills add pilot617/awesome-claude-code-plugins --skill ui-ux-buildergit clone --depth 1 https://github.com/pilot617/awesome-claude-code-pluginsWrote 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/pilot617/awesome-claude-code-plugins/ui-ux-builder)<a href="https://agentmods.dev/skills/pilot617/awesome-claude-code-plugins/ui-ux-builder"><img src="https://agentmods.dev/badge/skills/pilot617/awesome-claude-code-plugins/ui-ux-builder.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 | $0.00045 | $0.01848 |
| Opus 5 | $0.00023 | $0.00924 |
| Sonnet 5 | $0.00009 | $0.00370 |
| Haiku 4.5 | $0.00005 | $0.00185 |
Grade B, and why
ui-ux-builder scanned grade B with 1 finding 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 4d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
Just resolve `$PYTHON` and `$TOOL` as described in Prerequisites, then run any command from the Quick Reference table. How it starts
The opening of the file, as written. The whole thing — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ui-ux-builder — Full-Lifecycle UI/UX Builder
Full-lifecycle UI/UX skill: requirements gathering -> design plan -> user alignment -> implementation -> visual validation using Playwright.
When to Use
- Build or redesign UI for a web application
- Validate web app appearance against design specs
- Take screenshots of web pages
- Navigate and inspect page structure
- Compare implemented UI against design plans
- Check responsive layouts across breakpoints
Prerequisites
- Python 3.10+ (system
python3or any project virtual environment) - Playwright + Chromium:
pip install playwright && python -m playwright install chromium - The screenshot tool is at
${CLAUDE_PLUGIN_ROOT}/skills/ui-ux-builder/scripts/screenshot.py - The UX plan template is at
${CLAUDE_PLUGIN_ROOT}/skills/ui-ux-builder/template.md - A sample completed plan is at
${CLAUDE_PLUGIN_ROOT}/skills/ui-ux-builder/examples/sample.md
Resolving Paths
NEVER hardcode absolute paths. Always resolve dynamically:
- Set
TOOL="${CLAUDE_PLUGIN_ROOT}/skills/ui-ux-builder/scripts/screenshot.py" - Find Python by searching the project root in order:
venv/bin/python.venv/bin/python- Any
venv_*/bin/python - Fall back to system
python3
- Set
PYTHONto the first match found - Use
$PYTHON $TOOLin all commands
Example:
# Auto-detect python
if [ -f "venv/bin/python" ]; then PYTHON="venv/bin/python"
elif [ -f ".venv/bin/python" ]; then PYTHON=".venv/bin/python"
else PYTHON="python3"; fi
TOOL="${CLAUDE_PLUGIN_ROOT}/skills/ui-ux-builder/scripts/screenshot.py"
$PYTHON $TOOL http://localhost:3000 -o homepage.png
Workflow
Follow this 6-phase lifecycle:
digraph ui_ux_lifecycle {
rankdir=LR;
node [shape=box, style=rounded];
gather [label="1. Gather\nRequirements"];
plan [label="2. Create\nUX Plan"];
align [label="3. Align\nwith User"];
implement [label="4. Implement\nFrontend"];
validate [label="5. Validate with\nPlaywright"];
review [label="6. Review\nwith User"];
gather -> plan -> align -> implement -> validate -> review;
review -> implement [label="iterate", style=dashed];
align -> plan [label="revise", style=dashed];
}
What ships with it
4 files 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.
- 4d ago First seen · 221 lines · 45 tokens per session scan B 51acc51a2b98
ui-ux-builder is a skill published in the GitHub repository pilot617/awesome-claude-code-plugins (7 stars, last pushed 6mo ago), licensed MIT. It adds 45 tokens to every session and 1,848 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
peekaboo
Provides runtime observation and interaction for native macOS interfaces through accessibility state and screenshots. Use when the task depends on visible or interactive state in a running SwiftUI/AppKit app: what is rendered, focused, selected, enabled, reachable through menus/windows/dialogs, or experienced across a…
electron-playwright-validator
This skill should be used when a user asks to launch, inspect, automate, test, validate, or debug an Electron desktop UI through Playwright/CDP, including blank renderers, runtime import failures, accessibility snapshots, layout defects, click-through flows, or post-change checks. Not for native macOS or mobile apps…
swiftui-expert
This skill should be used when SwiftUI work requires judgment about Observation and state ownership, view identity or lifecycle, navigation, app-target concurrency, persistence, Apple-platform behavior, accessibility, performance, or architecture. Trigger on "review this SwiftUI screen", "why isn't this view…
design-sprint
Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate before we build", "rapid prototype", "test with users", or "should we build this". Also trigger when a team is stuck in endless debate over a high-stakes product…
hooked-ux
Design habit-forming product loops using the Hook Model (Trigger, Action, Variable Reward, Investment). Use when the user mentions "users arent coming back", "habit formation", "engagement loops", "habit zone", or "the manipulation matrix". Also trigger when designing notification or re-engagement strategies, building…
create-website
Guided journey from a blank page to a live, high-converting website, built message-first, then design, then conversion. Orchestrates ten skills phase by phase - one-page-marketing, storybrand-messaging, made-to-stick, top-design, web-typography, refactoring-ui, ux-heuristics, cro-methodology, scorecard-marketing…