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 ECD5A/OrchestrUI --skill ui-library-routergit clone --depth 1 https://github.com/ECD5A/OrchestrUIWrote 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/ecd5a/orchestrui/ui-library-router)<a href="https://agentmods.dev/skills/ecd5a/orchestrui/ui-library-router"><img src="https://agentmods.dev/badge/skills/ecd5a/orchestrui/ui-library-router/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/ecd5a/orchestrui/ui-library-router"><img src="https://agentmods.dev/badge/skills/ecd5a/orchestrui/ui-library-router.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.00064 | $0.00506 |
| Opus 5 | $0.00032 | $0.00253 |
| Sonnet 5 | $0.00013 | $0.00101 |
| Haiku 4.5 | $0.00006 | $0.00051 |
Grade A, and why
ui-library-router 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 8d 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.
What it actually says
UI Library Router
Inspect the host before selecting anything: framework, package manager, installed dependency versions, React/Tailwind versions, current design system, components.json, theme tokens, chart/motion dependencies, accessibility constraints and asset rights. Classify each requested feature as base UI, product component, marketing enhancement, data visualization, creative effect, bespoke motion or interactive vector graphics.
Normalize this evidence into HostProfile and TaskProfile before formal selection. When the OrchestrUI MCP is available, call recommend_stack with those structured profiles and retain its role ownership, rejected candidates, rule IDs and evidence. Use task-text inference only when project evidence is genuinely unavailable; do not treat a legacy-text-inference result as equivalent to inspected structured routing.
Choose the smallest set with one owner per major role. Existing systems win unless migration is explicit. Review evidence-bearing candidate rankings for installed reuse, dependency/bundle cost, overlap and bounded version compatibility, but never use score to override a hard compatibility, conflict or asset-rights gate. Use Bklit for data visualization; daisyUI only as an intentional semantic Tailwind base; Kokonut for selective shadcn-compatible product polish; Magic UI for the primary marketing enhancement layer; React Bits for one or two signature creative effects; Anime.js only for bespoke timelines/SVG/scroll work; Rive only for meaningful state-machine graphics with recorded .riv rights.
Never select all seven by default. Do not add daisyUI beside a shadcn-derived base without an explicit isolation or migration strategy. Prefer CSS and component-native motion before Anime.js. Never silently use Pro material or vendor, mirror, bundle, sublicense or redistribute React Bits components from OrchestrUI.
Return: existing stack; selected libraries and role ownership; required components/effects; official retrieval method; rejected redundancies; compatibility/legal risks; and a validation plan. A valid recommendation may select no OrchestrUI library.
Read references/libraries.md when evaluating ecosystem-specific tradeoffs. Read references/selection-workflow.md when producing a formal routing plan.
What ships with it
2 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.
- 8d ago First seen · 19 lines · 64 tokens per session scan A cda9be575cde
ui-library-router is a skill published in the GitHub repository ECD5A/OrchestrUI (1 stars, last pushed 5d ago), licensed MIT. It adds 64 tokens to every session and 506 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
daisyui-colors
Color rules that you must use with daisyUI 5.
daisyui-config
Configuration options for daisyUI 5.
web-prototype-taste-brutalist
Swiss industrial-print web prototype. Newsprint canvas, monolithic black grotesque, viewport-bleeding numerals, hairline grid dividers, hazard-red accent, ASCII syntax decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Swiss Industrial Print mode).
seed-design
An integration guide for SEED Design, covering shared component specifications and foundations plus React and Lynx implementation guidance.
seed-token-analysis
A read-only analyzer for one SEED color token, including its definitions, aliases, dependent tokens, component uses, generated outputs, and color contrast. A design token is a named value such as a color that can be reused across an interface.
ss-studio
Turn a product brief and optional references into three distinct creative directions, a human-selected StyleSeed interaction plan, generated image/video asset jobs, a working UI prototype, and a verified prototype-first showcase reel. Use for client concepts, app interaction exploration, trendy but coherent UI…