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 commands/laith0003/ux-skill/ux-framegit clone --depth 1 https://github.com/Laith0003/ux-skillWrote 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/commands/laith0003/ux-skill/ux-frame)<a href="https://agentmods.dev/commands/laith0003/ux-skill/ux-frame"><img src="https://agentmods.dev/badge/commands/laith0003/ux-skill/ux-frame.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00119 | $0.02070 |
| Opus 5 | $0.00060 | $0.01035 |
| Sonnet 5 | $0.00024 | $0.00414 |
| Haiku 4.5 | $0.00012 | $0.00207 |
Grade A, and why
ux-frame 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 5d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ux-frame
You are running the /ux-frame command from the ux plugin. The job is to produce a tight, structured framing block that every downstream command can read. No design work happens here. No critique. Just the four-field intake that turns a vague request into a working brief.
When to use
Triggers: "frame this", "what's the brief", "set up the project", "framing", "what are we actually building", "frame the work", "scope this".
Use at the start of any project, sprint, or one-off engagement. Also use mid-stream if a conversation has drifted and nobody can answer "who is this for and what changes when we ship?"
Input
Anything the user has: a Slack paste, a Figma URL, a one-line idea, a ticket, a meeting transcript, or nothing. If the input already contains the four framing fields, extract them — do not re-ask.
Process
1. Extract or ask — never both
Read what the user provided. If you can confidently pull audience, outcome, hypothesis, and success_signal out of the input, skip ahead to step 3.
If any field is missing, ask ONCE with a single combined question that surfaces all gaps. Example:
"Quick framing — who specifically is this for (not 'users'), what changes for them when we ship, what's your bet on why this will work, and how will we know it worked? One paragraph is fine."
Do not ask the four questions in four separate messages. That is the failure mode this command exists to prevent.
2. Sharpen the answers
Apply these tests before accepting any field:
- Audience — must name a real person/role/segment. Reject "everyone," "users," "people," "customers" without further qualifier. Push back specifically: "Which customers? Returning ones? First-time? A specific tier?"
- Outcome — must describe a behavior or state change for the audience, not a feature. Reject "make it better," "improve UX," "modernize." Push back: "What does the audience do differently after we ship that they don't do today?"
- Hypothesis — must include a causal "because" or "if-then." Reject "we think it'll be good." Push back: "What's the bet? If we change X, then Y will happen because Z."
- Success signal — must name a measurable thing or an observable behavior. Reject "users will love it." Push back: "What metric, behavior, or signal would prove this worked? How would you know in two weeks?"
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.
- 5d ago First seen · 183 lines · 119 tokens per session scan A 0f8dedb8a176
ux-frame is a command published in the GitHub repository Laith0003/ux-skill (65 stars, last pushed 1mo ago), licensed MIT. It adds 119 tokens to every session and 2,070 once invoked, about $0.0006 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 commands, from other repositories
ds-add
Kullanıcı bir Figma linki ile yeni tasarım sistemi eklemek istediğinde bu komutu kullan. Bu komut yeni ekleme ve güncelleme arasındaki farkı otomatik tespit eder.
ds-sync
Mevcut bir tasarım sistemi kütüphanesini Figma'dan senkronize eder. Tam sync, kısmi sync ve resume (yarım kalanı devam ettirme) destekler.
ds-validate
Kullanıcı "kütüphane doğrula", "DS'i validate et", "cache'i kontrol et", "DS uyumunu denetle" dediğinde bu komutu uygula. Eklenmiş DS'lerin repo template + user-local cache + state dosyalarının birbiriyle tutarlı olduğunu denetler.
add-library
Kullanıcı "kütüphane ekle", "library ekle", "tasarım sistemi ekle", "design system ekle" dediğinde bu komutu uygula.
setup-rest-token
Kullanıcı "REST token kur", "REST token setup", "FIGMARESTTOKEN nasıl ayarlanır", "component discovery hızlandır" dediğinde bu komutu uygula.
install-library
Kullanıcı "kütüphane kur", "library kur", "library install", "kütüphane yükle", "kütüphane güncelle" dediğinde veya bir .md dosya yolu verip "bunu kur" dediğinde bu komutu uygula.