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-reference-packsgit 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-reference-packs)<a href="https://agentmods.dev/skills/orkas-ai/orkas/ui-reference-packs"><img src="https://agentmods.dev/badge/skills/orkas-ai/orkas/ui-reference-packs/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-reference-packs"><img src="https://agentmods.dev/badge/skills/orkas-ai/orkas/ui-reference-packs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00920 |
| Opus 5 | $0.00002 | $0.00460 |
| Sonnet 5 | $0.00001 | $0.00184 |
| Haiku 4.5 | $0.00000 | $0.00092 |
Grade A, and why
ui-reference-packs 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 10d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ui-reference-packs
Use this skill after ui-design-contract only when UIDesigner needs a visual-system reference, product pattern, or style benchmark. It adapts OpenDesign's design-system and template catalogue into a small routed reference layer for HTML-first UI work.
This skill does not copy OpenDesign templates or brand systems. It helps choose a direction, then ui-design-executor turns that direction into original UI; load a design-system or deep renderer specialist only when separately triggered.
If ui-design-source has produced a frame/component handoff, use that handoff as stronger evidence than any reference pack. If an existing app already has clear tokens and components, skip this skill unless the user asks for a new style direction. If ui-live-artifact has not classified the task as live-ready or connected-live, do not select the live-artifact pattern.
Resource Map
Read only the relevant reference:
- Design-system packs — read when choosing a curated visual-system archetype.
- Pattern library — read when the user or design contract supports a specific page or artifact pattern.
Selection Workflow
- Decide whether a pack is needed.
- Use a pack when the user supplied references/brand material, asked for a style benchmark, the product has no clear visual system, or a broad pattern label must be accepted/rejected explicitly.
- Skip packs when the screenshot or repo system already gives enough visual direction.
- Start from the design contract.
- Screenshot/page structure, user-provided constraints, and repo tokens outrank reference packs.
- If no contract exists for a reference-heavy task, create one with
ui-design-contractfirst.
- Choose at most one primary design-system pack.
- Optionally add one secondary influence for typography, density, or motion.
- Do not blend many archetypes; blended taste turns generic quickly.
- Use neutral archetype IDs in handoff notes instead of brand names.
- Choose a page pattern only when the contract or user explicitly supports it.
- Dashboard, kanban, pricing, mobile-frame, wireframe, and live-artifact patterns have narrow triggers.
- A pattern is a structural permission, not a mandate.
- Convert the chosen pack into UIDesigner tokens.
- Color roles, type roles, spacing, radius, border, elevation, motion, and component behavior must be expressed in the local HTML/app system.
- Do not copy logos, exact layouts, product claims, screenshots, or proprietary components.
- Record the selection in the handoff.
- Name the selected pack.
- Explain why it fits.
- State what was rejected and why.
- Include any trigger guardrails, especially when not using a dashboard/kanban/pricing template.
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.
- 10d ago First seen · 70 lines · 4 tokens per session scan A 106817c7ea8b
ui-reference-packs is a skill published in the GitHub repository Orkas-AI/Orkas (1,848 stars, last pushed yesterday), licensed MIT. It adds 4 tokens to every session and 920 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.
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.