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 frontend-designgit 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/frontend-design)<a href="https://agentmods.dev/skills/orkas-ai/orkas/frontend-design"><img src="https://agentmods.dev/badge/skills/orkas-ai/orkas/frontend-design/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/frontend-design"><img src="https://agentmods.dev/badge/skills/orkas-ai/orkas/frontend-design.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.00002 | $0.04929 |
| Opus 5.5 | $0.00001 | $0.01972 |
| Sonnet 5.5 | $0.00000 | $0.00986 |
| Haiku 4.5 | $0.00000 | $0.00493 |
Grade A, and why
frontend-design 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 1mo 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
frontend-design
Use this as the design-lead layer for VideoStudio COMPOSE work. It shapes project/composition/composition-manifest.json::art_direction and the model-authored HTML/SVG motion graphics in index.html.
This skill does not pick the video production line, replace video-craft, or relax Orkas renderer constraints. If there is a conflict, renderer determinism, safe zones, legibility, audio ownership, and user-approved creative direction win.
Generation references
Read only the references required by the current composition:
- HTML generation playbook — read before filling reference-led
art_directionand before coding every non-trivial COMPOSE deliverable, so the scene plan and HTML use the same frame-composition decisions. - Visual primitives — read when selecting reusable CSS/SVG composition primitives and scene grammar.
- Worked compositions — read when examples are needed to turn subject matter into a cohesive visual system without copying a fixed template.
These references improve the initial generation. They do not create a new artifact, user gate, or approval step. Keep the art-direction pass internal and record only the decisions needed to make the manifest art direction executable.
Reference-led direction
Choose the design path before filling the fields below:
- Concrete reference: use the inspected source as the visual thesis; skip inventing a new visual style. Derive palette, light/dark scene distribution, typography hierarchy, layout and scene grammar from observed frames, then adapt the target product's confirmed content and explicit user changes. Fill each existing scene
compositionfrom its mapped source frame: dominant regions, relative placement/scale, surface organization and visual hierarchy. Replace the content inside that arrangement; do not substitute a new diagram or card layout to illustrate the same idea. Approval of a content outline does not authorize wholesale redesign. An inferred guide keeps recognizable attributes without becoming exact reproduction. - No concrete reference: choose an original thesis using the design traditions, anti-template preferences and examples below and in the generation references. These originality preferences never reject an observed source choice; renderer correctness and readability still apply to both paths.
What ships with it
3 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.
- 1mo ago Changed · +3 lines 82592d5d4789
- 1mo ago First seen · 203 lines · 2 tokens per session scan A ad7fc694e3b3
frontend-design is a skill published in the GitHub repository Orkas-AI/Orkas (2,165 stars, last pushed yesterday), licensed MIT. It adds 2 tokens to every session and 4,929 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.