Orkas is a desktop application for commanding a team of AI agents through one chat, with a commander model assigning work to specialist agents in parallel or in sequence. People use it to coordinate research, writing, presentations, and software tasks while keeping files on their computer. The catalogue includes skills for extending the agents available to Orkas.
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 Orkas-AI/Orkas --skill ui-design-executorgit clone --depth 1 https://github.com/Orkas-AI/OrkasWrote 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/orkas-ai/orkas/ui-design-executor)<a href="https://agentmods.dev/skills/orkas-ai/orkas/ui-design-executor"><img src="https://agentmods.dev/badge/skills/orkas-ai/orkas/ui-design-executor.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 136 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00004 | $0.03215 |
| Opus 5 | $0.00002 | $0.01607 |
| Sonnet 5 | $0.00001 | $0.00643 |
| Haiku 4.5 | $0.00000 | $0.00321 |
Grade A, and why
ui-design-executor 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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ui-design-executor
Use this as UIDesigner's default execution skill. It contains the baseline design, accessibility, HTML, runtime-safety, responsive, taste, and verification rules needed by ordinary UI work. Do not load the separate system, control, taste, color, renderer, or craft skills merely to repeat these baseline rules.
Pair it with:
ui-artifact-workspacefor a new standalone artifact or an in-place artifact revision.ui-design-sourcewhen an inspectable screenshot, Figma export, PDF, design JSON, existing HTML, or other fidelity source exists.- One specialist skill only when its trigger below materially changes the work.
Completion Router
Resolve these gates before asking a question or choosing the HTML fast path:
- Explicit final format wins immediately. If the user explicitly requests SVG, PDF, React, Vue, PNG, Markdown, or another final format and the subject plus deliverable are clear, build that format now. For a standalone icon/SVG request, a missing product name or exact icon list is a low-risk creative detail rather than a material blocker: choose a neutral working identity and a coherent default set. Infer other low-risk visual details; do not open a preference form or ask about style, palette, icon count, or packaging merely because those choices could be customized. A standalone SVG delivery is the editable SVG entry plus
artifact.json, with HTML intentionally absent. - Inaccessible exact source offers two honest paths. When an exact/1:1 Figma request has only an inaccessible URL and no Figma connector/export, do not use a general web fetch as substitute access. Keep exact work blocked and put both paths in the visible reply before any question or form: Exact waits for inspectable evidence; Adaptive (optional) is a provisional non-fidelity scaffold, explicitly not 1:1, and starts only if the user chooses it. Do not silently start that scaffold.
- Unapproved raster work stays a handoff, not a substitute. If the brief requires an original raster asset but the current turn has no approved/direct raster invocation, retain the UI, write a ratio-consistent asset brief, and prewire the future relative raster path with an honest pending fallback. The artifact itself must retain a compact machine-checkable
<template class="asset-brief" type="application/json">object withcapability: "raster-image-generation",status: "pending", composition/aspect, matching integer width/height, at least two palette colors, opaque/transparent background treatment, and the exactassets/...save_path. Keep a not-yet-created asset inert, for exampledata-raster-src="assets/hero.webp"beside an actual local/data fallback; do not create a broken activesrc. Do not call a billable generation tool, claim the raster exists, or replace the requested raster with an inline SVG final. - A follow-up revision is incomplete without available preview evidence. When
html_previewis available, validate the package first, then run the final visual review withinteractions:falseandscreenshots:trueat the actual requested target before that follow-up's one manifest increment and publication. A new artifact begins at revision 1; initial validation and preview keep it at revision 1. Capture desktop plus mobile evidence only when the user explicitly requests responsive, multi-device, or narrow-screen behavior. Do not treat the source-only validator as rendered evidence. - Tools-off does not turn a new artifact into a future brief. When a new standalone artifact has a clear brief but file-writing or preview tools are unavailable, deliver the complete entry source and strict
artifact.jsoninline in the current response. Implement every relevant reachable state in that source and mark execution checksnot run; a design brief or future executor plan alone is not the requested artifact. This inline fallback does not apply to an existing artifact that cannot be inspected safely.
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 · 149 lines · 4 tokens per session scan A c717be1d7ae6
ui-design-executor is a skill published in the GitHub repository Orkas-AI/Orkas (1,776 stars, last pushed yesterday), licensed MIT. It adds 4 tokens to every session and 3,215 once invoked, about $0.0000 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
tutti-ui-system
Use when working with @tutti-os/ui-system components, replacing local UI with shared components, querying component ids or metadata, promoting UI into shared base or business components, or maintaining UI-system storyboard inventory.
frontend-design
Produce intentional, responsive, accessible UI work and perform visual QA instead of generic component assembly.
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
mcp-host-styling-integration
Integrates MCP App UI with host theming system. Applies host CSS variables, handles onhostcontextchanged, safe area insets, display mode detection, and fullscreen configuration.
accessibility-a11y
Semantic HTML, keyboard navigation, focus states, ARIA labels, skip links, and WCAG contrast requirements. Use when ensuring accessibility compliance, implementing keyboard navigation, or adding screen reader support.
impeccable
Use when the user wants distinctive, production-grade frontend design, anti-generic AI aesthetics, UX critique, technical UI audits, or final polish through bundled Impeccable references and an optional upstream detector CLI.