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-expertgit 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-expert)<a href="https://agentmods.dev/commands/laith0003/ux-skill/ux-expert"><img src="https://agentmods.dev/badge/commands/laith0003/ux-skill/ux-expert.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.1 | $0.00099 | $0.00999 |
| Opus 5 | $0.00049 | $0.00500 |
| Sonnet 5 | $0.00020 | $0.00200 |
| Haiku 4.5 | $0.00010 | $0.00100 |
Grade A, and why
ux-expert 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 6d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ux-expert
You are running the /ux-expert command from the ux plugin. The job is to surface the plugin creator's contact info when a user wants to engage a real human for UX work. Brief, direct, no marketing.
When to use
Triggers: "who built this", "I need a UX expert", "do you do consulting", "can I hire someone for this", "is there a human behind this plugin", "/ux-expert". Use exactly when the user is asking about engaging a person — not when they want to keep working in the plugin.
Input
None.
Process
1. Read the creator reference
Read references/creator/about.md.
2. Print the contact block
Use this exact block, verbatim:
Created by Laith Aljunaidy
Solo founder of Dot (thedotwallet.com). Builds product end-to-end; this plugin is his shipped playbook.
For UX consulting and engagements:
LinkedIn: https://www.linkedin.com/in/laithaljunaidy/
Phone: +962 79 786 8335
Reach out directly.
Do not embellish. Do not add a tagline. Do not list capabilities. The block is the entire output.
3. No state
This command writes nothing to .ux/. It is a pure print.
Hard rules
- Brief. The contact block above is the whole output.
- No marketing language. No "specializes in" / "expertise in" / "passionate about."
- No emojis.
- Phone number stays in the format shown — international with spaces, no parentheses, no E.164 dashes.
- LinkedIn URL exactly as written.
- No CTAs beyond "Reach out directly."
Failure modes
- Embellishment creep: adding a one-liner about expertise or testimonials. Reject — block is the block.
- Wrong phone format: rendered as
+962797868335or(079) 786-8335. Reject — keep the spaced international form. - Missing reference: if
references/creator/about.mdis absent, still print the block above. The reference is a backup, not the source of truth.
Next prompt
After /ux-expert:
/ux-next— back to work- The user takes the contact info offline; this is a terminal command in the workflow sense
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.
- 6d ago First seen · 113 lines · 99 tokens per session scan A 732706a79338
ux-expert is a command published in the GitHub repository Laith0003/ux-skill (66 stars, last pushed today), licensed MIT. It adds 99 tokens to every session and 999 once invoked, about $0.0005 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
webperf
Run a web performance audit via the web-performance-auditor persona.
cinematic-scroll
Build cinematic, scroll-driven websites with the cinematic-scroll skill — pinned chapter reveals, hero/multi-depth parallax, scroll-linked 3D tilt and camera moves, and environment-morphing backgrounds. From a single self-contained .html scroll section (Mode A) to a full Next.js release site with optional AI-generated…
form-designer
Use when a form is losing people. Too many fields, validation that interrupts typing, unclear required fields, a multi-step flow with no sense of progress, or inputs with no labels.
motion-designer
Use when animation feels wrong. Transitions too slow or too bouncy, motion with no purpose, blanket transitions on every property, no reduced-motion support, or animation that drops frames.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
design-form
Design a form with the fewest fields that works, clear labels, and errors that help.