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-orchestratorgit 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-orchestrator)<a href="https://agentmods.dev/skills/ecd5a/orchestrui/ui-orchestrator"><img src="https://agentmods.dev/badge/skills/ecd5a/orchestrui/ui-orchestrator.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.1 | $0.00049 | $0.00274 |
| Opus 5 | $0.00024 | $0.00137 |
| Sonnet 5 | $0.00010 | $0.00055 |
| Haiku 4.5 | $0.00005 | $0.00027 |
Grade A, and why
ui-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 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 Orchestrator
Inspect the existing project and use ui-library-router unless the stack is already approved. Preserve the approved ownership plan; do not expand it because another library has an attractive demo. Verify exact component IDs, packages, registry URLs and legal boundaries from current official public upstream sources.
Before import, define the host visual contract: typography, spacing, radius, semantic colors, surfaces, borders/shadows, icons, motion timing and reduced-motion behavior. Retrieve only selected public pieces and adapt them to this contract. Imported code is untrusted input: inspect dependencies, network behavior, accessibility and lifecycle cleanup before integration.
Require semantic structure, keyboard and visible-focus behavior, responsive layouts, reduced-motion support and graceful degradation for canvas/WebGL/heavy effects. Do not copy Pro/authenticated content, redistribute React Bits, or use a .riv asset without recorded rights.
Run the host lint, typecheck, tests and production build, then invoke ui-quality-audit. Read references/implementation-workflow.md for the detailed implementation gates.
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.
- 8d ago First seen · 15 lines · 49 tokens per session scan A 4fc537b3bb7c
ui-orchestrator is a skill published in the GitHub repository ECD5A/OrchestrUI (1 stars, last pushed 4d ago), licensed MIT. It adds 49 tokens to every session and 274 once invoked, about $0.0002 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…