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-live-artifactgit 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-live-artifact)<a href="https://agentmods.dev/skills/orkas-ai/orkas/ui-live-artifact"><img src="https://agentmods.dev/badge/skills/orkas-ai/orkas/ui-live-artifact/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-live-artifact"><img src="https://agentmods.dev/badge/skills/orkas-ai/orkas/ui-live-artifact.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.01145 |
| Opus 5 | $0.00002 | $0.00573 |
| Sonnet 5 | $0.00001 | $0.00229 |
| Haiku 4.5 | $0.00000 | $0.00114 |
Grade A, and why
ui-live-artifact 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 12d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ui-live-artifact
Use this skill when the user asks for a live dashboard, refreshable report, synced view, recurring data artifact, connector-backed UI, auditable status page, or data-backed HTML that should remain useful after the first render.
Do not use this for ordinary one-off mockups, static redesigns, image-to-HTML conversion, or visual polish. In those cases ui-design-executor is enough.
Intent Gate
Choose the mode before creating files:
static_html: one-off HTML design or mockup. No refresh contract.live_ready_html: HTML plus data/provenance contract that can later be wired to refresh, but no live runtime registration happens now.connected_live: only when Orkas exposes an actual connector/runtime for the requested source in the current context.
If the request is ambiguous, ask one short question: "Should this be refreshable/live, or just a static HTML design?"
Required Source Questions
Resolve:
- Audience and decision the view supports.
- Data source: local file, repo data, connector, manual sample, or unknown.
- Freshness expectation: manual, on open, hourly/daily, or event-driven.
- Refresh owner: user, connector, scheduled job, or future integration.
- Privacy level: public, workspace, sensitive, or regulated.
Do not ask for secrets. If a connector is not available, ask the user to connect/provide an export rather than requesting API keys.
File Contract
For live_ready_html, create or describe these files when a file deliverable is requested:
index.html: rendered preview that works now in the Orkas embedded artifact surface.template.html: optional source template when the user wants future refresh wiring.data.json: compact normalized preview data only.artifact.json: optional metadata for title, description, refresh mode, view type, and safe source descriptors.provenance.json: optional safe summary of source, transform, timestamp, confidence, and omitted sensitive fields.
If no file workspace is available, embed the same contract in the HTML artifact and final handoff.
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.
- 12d ago First seen · 101 lines · 4 tokens per session scan A 468d4b9ee406
ui-live-artifact is a skill published in the GitHub repository Orkas-AI/Orkas (1,911 stars, last pushed yesterday), licensed MIT. It adds 4 tokens to every session and 1,145 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-workspace-app-factory
Create, convert, or repair one Tutti workspace app as either a self-contained publishable package under package/ or a Chrome-style local debug app under .tutti/dev-app/. Use for mention://workspace-app-factory/create handoffs, mention://workspace-app-factory handoffs, standalone app generation, adapting existing…
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.
tutti-agent-workspace-app
Build or evolve a complex agent-enabled Tutti workspace app repository. Use for Tutti apps with web/server/shared monorepos, @tutti-os/agent-acp-kit local agent runtimes, kit-owned TUTTICLI agent/composer discovery, dynamic agent catalogs, run-scoped MCP tool gateways, app-owned package builders, web-first debugging…
takt
A workflow engine that runs a task through a sequence of steps defined in a YAML file, using separate coding agents for the work.
takt
A workflow engine for coordinating multiple coding agents. It reads a YAML workflow, a text configuration format, and moves agents through its defined steps and rules.
create-coordclaw-team
A Skill for creating a CoordClaw multi-agent collaborative team. Through an 8-step standardized process, from requirement gathering to team validation, rapidly build a complete AI team.