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 sergekostenchuk/ui-ux-agent-skill-system --skill senior-ui-ux-orchestratorgit clone --depth 1 https://github.com/sergekostenchuk/ui-ux-agent-skill-systemWrote 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/sergekostenchuk/ui-ux-agent-skill-system/senior-ui-ux-orchestrator)<a href="https://agentmods.dev/skills/sergekostenchuk/ui-ux-agent-skill-system/senior-ui-ux-orchestrator"><img src="https://agentmods.dev/badge/skills/sergekostenchuk/ui-ux-agent-skill-system/senior-ui-ux-orchestrator/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/sergekostenchuk/ui-ux-agent-skill-system/senior-ui-ux-orchestrator"><img src="https://agentmods.dev/badge/skills/sergekostenchuk/ui-ux-agent-skill-system/senior-ui-ux-orchestrator.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.00222 | $0.01611 |
| Opus 5 | $0.00111 | $0.00805 |
| Sonnet 5 | $0.00044 | $0.00322 |
| Haiku 4.5 | $0.00022 | $0.00161 |
Grade A, and why
senior-ui-ux-orchestrator 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 12d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Senior UI/UX Orchestrator
This is the main entrypoint for the UI/UX skill group. Classify the user request first, choose the smallest specialist set that can solve it, enforce privacy/evidence rules, and return a concise implementation or audit handoff.
Operating Modes
route: choose one or more specialist skills.plan: create or update a UI/UX skill-system plan.build-webapp: route product UI work towebapp-ui-skill.build-marketing: route public page work tomarketing-site-skill.audit: route evidence-backed review toux-audit-skill.critique: route visual quality review todesign-critic-skill.figma: route Figma context, MCP, canvas, asset, effect, and design-system work tosenior-figma-orchestrator.design-intelligence: route style, pattern, typography, color, and UI precedent research toui-ux-pro-max.stitch: route Stitch or AI UI exploration tostitch-design-bridgeafter UX/product and design-intelligence constraints exist.three-variant-design: coordinate exactly three distinct design directions before Stitch, Figma, or code execution.council: convene a senior UI/UX/SEO/LLM/Figma/implementation council when cross-skill recommendations conflict.wiki-context: capture large-project context into the Obsidian/LLM wiki after decisions, without secrets.interactive-effect: route cursor/mask/reveal frontend effects tocursor-reveal-hero.image-alignment: route base/reveal image suitability checks toimage-layer-alignment-validator.verify: check reports, commands, artifacts, and fake-evidence risk.
Required Workflow
- Read references/routing-decision-framework.md.
- If the request is large, cross-domain, asks for three variants, uses Stitch, or contains conflicting UI/UX/SEO/Figma/code recommendations, read references/cross-skill-council-contract.md.
- If the request is ambiguous, use assets/intake-questions.md and ask only blocking questions.
- If deterministic classification helps, run scripts/classify_product_type.py on the prompt and write
reports/intake.json. - Apply the shared privacy policy from
../../shared/privacy-policy.md. - Route to the relevant specialist skill and state why.
- For Stitch workflows, require product/UX, SEO/LLM if public, and
ui-ux-pro-maxconstraints before creating Stitch prompts. - For large multi-session projects, add a wiki context gate after major decisions and before final handoff; never store API keys, tokens, private screenshots, or
.envdata. - Require evidence according to
../../shared/reporting-contract.md. - For material UI changes, require visual verification or record why it was skipped.
What ships with it
9 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.
- agents/openai.yaml 398 B
- assets/intake-questions.md 999 B
- assets/routing-rules.json 5.7 KB
- evals/evals.json 5.7 KB
- references/cross-skill-council-contract.md 6.9 KB
- references/near-miss-prompts.md 2.0 KB
- references/routing-decision-framework.md 4.9 KB
- scripts/classify_product_type.py 6.0 KB runs code
- scripts/validate_tool_inventory.py 3.3 KB runs code
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.
- 12d ago First seen · 90 lines · 222 tokens per session scan A 0f025034599e
senior-ui-ux-orchestrator is a skill published in the GitHub repository sergekostenchuk/ui-ux-agent-skill-system (23 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 222 tokens to every session and 1,611 once invoked, about $0.0011 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
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.