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-contractgit 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-contract)<a href="https://agentmods.dev/skills/orkas-ai/orkas/ui-design-contract"><img src="https://agentmods.dev/badge/skills/orkas-ai/orkas/ui-design-contract/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-contract"><img src="https://agentmods.dev/badge/skills/orkas-ai/orkas/ui-design-contract.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.00003 | $0.01858 |
| Opus 5 | $0.00002 | $0.00929 |
| Sonnet 5 | $0.00001 | $0.00372 |
| Haiku 4.5 | $0.00000 | $0.00186 |
Grade A, and why
ui-design-contract 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ui-design-contract
Use this skill before rendering when the direction must persist across multiple screens/components, brand or system work, conflicting references, formal handoff, or a genuinely vague visual system. Ordinary single-screen screenshots and clear briefs use ui-design-executor's compact source/visual thesis instead of loading a full durable contract.
The contract is not extra ceremony. It prevents generic templates, protects the user's reference intent, and gives the HTML artifact a stable design source of truth.
For standalone work, keep any long-lived DESIGN.md inside the canonical directory chosen by ui-artifact-workspace. On later revisions, read and update that contract in place only when the accepted design direction actually changes.
When the source is a Figma link/export, design JSON, PDF, or design-tool screenshot, use ui-design-source first so the contract is grounded in inspectable frames, components, variables, and fidelity boundaries.
When a visual benchmark or page pattern is needed, pair this skill with ui-reference-packs after the contract is drafted. Skip reference packs when the screenshot, repo tokens, or existing design system already provide enough direction. The contract decides what must be preserved; reference packs only help choose style DNA and pattern boundaries.
When To Create A Contract
Create a compact durable contract before HTML when any of these are true:
- The screenshot/reference spans multiple screens, must establish a reusable direction, or contains conflicting evidence that a compact executor snapshot cannot resolve.
- The user says "make it feel like this", "参考这个", "做同款但不照抄", or gives brand/style references.
- The request spans more than one screen, component family, or visual system.
- The user asks for a design system, brand board, logo/identity board, or implementation handoff.
- Existing app tokens/components are unclear and the agent must infer a direction.
If the user only asks for a tiny local UI tweak with a clear existing system, a full contract can be a short inline "contract snapshot".
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 · 160 lines · 3 tokens per session scan A 23d6d08d5f42
ui-design-contract is a skill published in the GitHub repository Orkas-AI/Orkas (1,848 stars, last pushed yesterday), licensed MIT. It adds 3 tokens to every session and 1,858 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.