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 agentmods add skills/microsoft/hve-core/ux-artifactsnpx skills add microsoft/hve-core --skill ux-artifactsgit clone --depth 1 https://github.com/microsoft/hve-coreWhat 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 | $0.00035 | $0.02411 |
| Opus 5 | $0.00017 | $0.01205 |
| Sonnet 5 | $0.00007 | $0.00482 |
| Haiku 4.5 | $0.00003 | $0.00241 |
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 3d 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 — 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
- Resolve
mode,project, andsubject. Ask one routing question only when the requested asset matches more than one mode. - Read references/evidence-model.md. Resolve the output path and ingest only the supplied
sourceor in-context evidence. - Load the selected mode reference. Produce its bounded asset without conducting coaching, interviews, technical conformance checks, or destination writes.
- 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. - When
destinationis 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. - Return the asset pointer, evidence summary, unresolved items, and destination intent when requested.
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.
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.
- 3d ago First seen · 139 lines · 35 tokens per session scan A 5b420e4024ad
ux-artifacts is a skill published in the GitHub repository microsoft/hve-core (1,411 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 2,411 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…