ui-artifact-workspace

ui-artifact-workspace is a skill for Claude Code, Codex from Orkas-AI/Orkas. It costs 5 tokens per session (2,864 once invoked), scanned A, original, MIT.

A workspace and packaging contract for standalone visual UI artifacts. It keeps each artifact in one stable directory with its source, assets, manifest, and revision history.

In plain words
What is it for?
Use it when creating or revising a standalone visual design or interface artifact, including its local assets, references, interactions, and versioned updates.
Why use it?
It prevents files and revisions from becoming scattered or disconnected. For follow-up changes, it requires preserving existing edits and checking that the updated artifact still renders correctly.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when creating or revising a standalone visual design or interface artifact, including its local assets, references, interactions, and versioned updates.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/orkas-ai/orkas/ui-artifact-workspace
About the project

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.

Orkas-AI/Orkas · 1,911 stars · on GitHub · orkas.ai

Install

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.

Any agent
npx skills add Orkas-AI/Orkas --skill ui-artifact-workspace
Clone the repo
git clone --depth 1 https://github.com/Orkas-AI/Orkas

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for ui-artifact-workspace

README.md
[![agentmods](https://agentmods.dev/badge/skills/orkas-ai/orkas/ui-artifact-workspace/github.svg)](https://agentmods.dev/skills/orkas-ai/orkas/ui-artifact-workspace)
Your own site
<a href="https://agentmods.dev/skills/orkas-ai/orkas/ui-artifact-workspace"><img src="https://agentmods.dev/badge/skills/orkas-ai/orkas/ui-artifact-workspace/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.

agentmods 80×15 button for ui-artifact-workspace

Your own site · 80×15
<a href="https://agentmods.dev/skills/orkas-ai/orkas/ui-artifact-workspace"><img src="https://agentmods.dev/badge/skills/orkas-ai/orkas/ui-artifact-workspace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 5 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,864 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00005 $0.02864
Opus 5 $0.00003 $0.01432
Sonnet 5 $0.00001 $0.00573
Haiku 4.5 $0.00001 $0.00286

Measured today against content hash b7f14f5543f4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

ui-artifact-workspace 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 today.

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.

resources/builtin/marketplace/agents/bcfcb4921dce/skills/ui-artifact-workspace/SKILL.md · 167 lines

How it starts

The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.

ui-artifact-workspace

Use this skill for every standalone UIDesigner artifact, regardless of final format, and for every follow-up that revises a previously created artifact. It is the continuity and packaging contract around the visual skills; it does not decide the visual direction itself.

The goal is one canonical artifact, one stable directory, and small traceable revisions. Do not scatter HTML, images, notes, and data across the workspace root. Do not make the user identify the same artifact again on every turn.

Follow-Up Non-Negotiable

Every revision response must preserve all three proof groups together; missing any group blocks delivery:

  1. Canonical reuse: read the current manifest/entry/assets and patch the same directory in place.
  2. Preservation: explicitly say fork/v2: forbidden and preserve named user edits plus unrelated hooks, interactions, tokens, and asset paths.
  3. Revision acceptance: requested visual change or state plus non-blank first render, requested viewport behavior, and local asset/reference resolution; increment the manifest once only after all pass.

When tools are off, emit the Revision Executor Contract near the start of the response. Every check remains not run but still includes its future action and concrete pass criterion. Do not output a replacement manifest with guessed fields or a reduced files list; describe the pending revision delta until the existing manifest has been read.

Choose The Canonical Workspace

Resolve the mode before editing:

  1. Follow-up to an existing artifact: reuse the exact artifact directory from the user's path, the current conversation, or its artifact.json. Inspect it before changing anything.
  2. Implementation inside an existing app repo — only when the user explicitly asked for changes to that repo's source: the real app source is canonical. Edit the existing components, tokens, and routes in place; do not create a parallel copy that can drift. Create a standalone ui-artifacts/<task-slug>/ preview only when the user also asks for a shareable design artifact. Without that explicit ask this mode is unavailable: the repo is read-only, and the work goes to mode 3 plus a change proposal.
  3. New standalone artifact: create ui-artifacts/<task-slug>/ under the current writable workspace. Use the supplied repo root only when repo writes were explicitly authorized; otherwise keep the directory outside the repo tree so a read-only repo stays untouched. Use a short stable kebab-case slug derived from the product or feature, not a timestamp.

Read the full file on GitHub · 167 lines

Changes

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.

  1. today Changed b7f14f5543f4
  2. 13d ago First seen · 167 lines · 5 tokens per session scan A ce24edbbfa76

Subscribe to this mod's changes

ui-artifact-workspace is a skill published in the GitHub repository Orkas-AI/Orkas (1,911 stars, last pushed yesterday), licensed MIT. It adds 5 tokens to every session and 2,864 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.