ux-artifacts

ux-artifacts is a skill for Claude Code from microsoft/hve-core. It costs 35 tokens per session (2,411 once invoked), scanned A, original, MIT.

A set of UX documents that turn supplied research and decisions into clear records of user needs, journeys, screen structure, inclusion concerns, or engineering handoffs.

In plain words
What is it for?
It helps document user needs, map journeys, sketch interface structure, review inclusion risks, and prepare implementation handoffs.
Why use it?
It keeps evidence, uncertainty, and decisions together so later practitioners or engineers do not have to guess or repeat the research.

Skill for Claude Code ✓ vendor

Written for Claude Code: user-invocable in frontmatter.

Good fit It helps document user needs, map journeys, sketch interface structure, review inclusion risks, and prepare implementation handoffs.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/microsoft/hve-core/ux-artifacts
About the project

HVE Core is a collection of agents, prompts, coding instructions, and skills for building repeatable software-development workflows with GitHub Copilot. It is intended for individuals and teams that want structured AI-assisted research, planning, implementation, and review, while the catalogue entries provide many of its reusable workflow components.

microsoft/hve-core · 1,606 stars · on GitHub

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 microsoft/hve-core --skill ux-artifacts
Clone the repo
git clone --depth 1 https://github.com/microsoft/hve-core

Made for: Claude Code.

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 ux-artifacts

README.md
[![agentmods](https://agentmods.dev/badge/skills/microsoft/hve-core/ux-artifacts/github.svg)](https://agentmods.dev/skills/microsoft/hve-core/ux-artifacts)
Your own site
<a href="https://agentmods.dev/skills/microsoft/hve-core/ux-artifacts"><img src="https://agentmods.dev/badge/skills/microsoft/hve-core/ux-artifacts/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 ux-artifacts

Your own site · 80×15
<a href="https://agentmods.dev/skills/microsoft/hve-core/ux-artifacts"><img src="https://agentmods.dev/badge/skills/microsoft/hve-core/ux-artifacts.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,411 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 warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Prompt Injection · line 89
    Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.
    Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00035 $0.02411
Opus 5.5 $0.00014 $0.00964
Sonnet 5.5 $0.00007 $0.00482
Haiku 4.5 $0.00003 $0.00241

Measured 2mo ago against content hash 5b420e4024ad, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ux-artifacts 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 2mo 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.

.github/skills/design-thinking/ux-artifacts/SKILL.md · 139 lines

How it starts

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

UX Artifacts

Produce one durable, evidence-labelled UX asset from supplied context. Use this skill directly or through an agent when the required outcome is an artifact rather than a coached conversation.

Goal

Turn supplied UX evidence and decisions into a current Markdown asset that another practitioner, agent, or engineer can consume without inventing research or losing uncertainty.

Modes

Load exactly one mode reference for each invocation.

Mode Outcome Reference
frame-needs Current context, user needs, desired outcomes, and known workarounds references/frame-needs.md
map-journey Staged journey with actions, thoughts, pain points, and opportunities references/map-journey.md
sketch-structure Surface composition, controls, interaction states, and transitions references/sketch-structure.md
decide-inclusion Concept-stage exclusion risks, demands, alternatives, and coverage gaps references/decide-inclusion.md
prepare-handoff Implementation-facing flow, states, recovery, rationale, and open decisions references/prepare-handoff.md

The modes are operations over supplied evidence. They are not practitioner roles, project phases, persistent workflows, or prerequisites for one another. Never invoke another mode automatically.

Flow

  1. Resolve mode, project, and subject. Ask one routing question only when the requested asset matches more than one mode.
  2. Read references/evidence-model.md. Resolve the output path and ingest only the supplied source or in-context evidence.
  3. Load the selected mode reference. Produce its bounded asset without conducting coaching, interviews, technical conformance checks, or destination writes.
  4. Write the current asset to .copilot-tracking/ux-artifacts/{project-slug}/{subject-slug}/{mode}.md. A rerun updates that file rather than creating dated duplicates or hidden state.
  5. When destination is supplied, read references/to-figma.md or references/to-mural.md and append destination intent to the result. Resolve the destination inputs that reference requires before producing intent. Do not invoke either destination.
  6. Return the asset pointer, evidence summary, unresolved items, and destination intent when requested.

Read the full file on GitHub · 139 lines

Files

What ships with it

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

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. 2mo ago First seen · 139 lines · 35 tokens per session scan A 5b420e4024ad

Subscribe to this mod's changes

ux-artifacts is a skill published in the GitHub repository microsoft/hve-core (1,606 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 2,411 once invoked, about $0.0001 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.

Related

ux-artifacts compared with skills from other repositories

ux-artifacts next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
ux-artifactsmicrosoft/hve-coreSkill1.6kyesterdayMITA35Claude Code
webgl-holographic-foilnexu-io/open-designSkill107kyesterdayApache-2.0A41Claude Code, Codex
html-ppt-hermes-cyber-terminalnexu-io/open-designSkill107kyesterdayApache-2.0A53Claude Code, Codex
html-ppt-taste-brutalistnexu-io/open-designSkill107kyesterdayApache-2.0A78Claude Code, Codex
visual-ralphYeachan-Heo/oh-my-codexSkill34kyesterdayMITA52Codex
glance-canonical-layoutsandroid/skillsSkill10k3d agoApache-2.0A56Claude Code
prototype-webnexu-io/html-anythingSkill9.5kyesterdayApache-2.0A24Claude Code, Codex