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-sourcegit 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-source)<a href="https://agentmods.dev/skills/orkas-ai/orkas/ui-design-source"><img src="https://agentmods.dev/badge/skills/orkas-ai/orkas/ui-design-source/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/orkas-ai/orkas/ui-design-source"><img src="https://agentmods.dev/badge/skills/orkas-ai/orkas/ui-design-source.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Privilege Escalation · line 145 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00003 | $0.03340 |
| Opus 5.5 | $0.00001 | $0.01336 |
| Sonnet 5.5 | $0.00001 | $0.00668 |
| Haiku 4.5 | $0.00000 | $0.00334 |
Grade A, and why
ui-design-source 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 7d 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ui-design-source
Use this skill when the user provides Figma material, design-export files, screenshots of design tools, PDFs, JSON, existing HTML or other UI source code, or asks for design-to-HTML/code fidelity. It adapts OpenDesign/Figma handoff discipline for UIDesigner without requiring a live source runtime.
This skill turns design-source evidence into a compact handoff for ui-design-executor. Add a durable contract, reference pack, design-system, or deep renderer skill only when its specialist trigger is present; do not fan an ordinary screenshot task out to all of them.
Access Rules
- If a Figma connector, MCP, plugin API, or exported file is actually available, inspect it with the available tool or file reader.
- If the user only provides a Figma URL and no available Figma access exists, do not probe it with general
web_fetch/browser search as substitute Figma access. Ask for a screenshot/export or continue only from visible notes. Do not claim "Figma imported", "frames inspected", or "variables read". Keep requestedexact/1:1 work blocked until inspectable evidence arrives. Always put both next paths in the visible response before any question/form: Exact waits for a connector, screenshot, PDF, or export; Adaptive (optional) can start only after the user chooses it. Offer anadaptiveprovisional scaffold as non-fidelity work; never call it 1:1. Do not silently start the adaptive path. - If the design source is an image or PDF, treat it like a screenshot: extract what is visible, label uncertain text/spacing, and preserve information architecture.
- If readable UI code exists, it is the primary structural reconstruction source even when the project cannot run. Trace its page/component tree, styles, assets, and visible states; use rendering as optional verification rather than a prerequisite.
Source Intake
Classify the source:
existing_product: an inspectable current application, repository UI, rendered route, component library, or design documentation that constrains unchanged product surfaces.existing_ui_code: HTML/CSS, JSX/TSX, Vue, Svelte, native declarative UI, or another readable presentation implementation that must be structurally translated into the requested deliverable.figma_url: URL or file key, not enough by itself unless a connector/tool is available.figma_export_json: nodes, components, variables, styles, constraints, or plugin export.design_screenshot: frame image, prototype screenshot, app screenshot, or reference image.design_pdf: exported specs, deck, or annotated design handoff.existing_html: current artifact, app page, or prototype.design_notes: Markdown/text PRD, redlines, specs, or designer comments.
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.
- 7d ago Changed · +2 lines 6d1195554fae
- 1mo ago Changed · +72 lines b81e9c749312
- 1mo ago First seen · 164 lines · 3 tokens per session scan A 3f181bcb5c96
ui-design-source is a skill published in the GitHub repository Orkas-AI/Orkas (2,165 stars, last pushed yesterday), licensed MIT. It adds 3 tokens to every session and 3,340 once invoked, about $0.0000 per session on Opus 5.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.
cross-border-listing-image-layout-audit
Audit listing image and layout notes — first-impression hero, info hierarchy, lifestyle vs studio, copy density, trust signals, compliance — into a follow-up checklist.
design-plan-review
Reviews a UI or UX plan before implementation.
excalidraw-diagram-generator
Converts textual concepts or workflows into clear diagram instructions suitable for Excalidraw or other visual tools.
infographic-builder
Turns textual content into structured infographic formats suitable for reports, presentations, and educational materials.
ui-ux-layout-advisor
Advises on interface layouts to optimize clarity, spacing, hierarchy, and usability.