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-initgit 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-init)<a href="https://agentmods.dev/commands/laith0003/ux-skill/ux-init"><img src="https://agentmods.dev/badge/commands/laith0003/ux-skill/ux-init.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.00042 | $0.00740 |
| Opus 5 | $0.00021 | $0.00370 |
| Sonnet 5 | $0.00008 | $0.00148 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
ux-init 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 4d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/ux-init — bootstrap ux-skill v2
One command. Three things.
- Detects which IDE you're using (
.claude/,.cursor/,.windsurf/, etc.) and installs the right artifacts for it. - Verifies the Python engine is reachable.
- Prints a stats snapshot showing what's in your data manifests.
When to use
- First time installing ux-skill v2 in a new project.
- After cloning a project that uses ux-skill, to ensure your local install matches.
- After a
pip install --upgrade uxskill, to wire new IDEs you've started using.
When to skip
- The project already has
.ux/installed.json(you're set up). - You only want to install for a specific IDE → use
ux install <ide-name>directly.
How it runs
# Inside a Claude Code session, the command runs:
python3 -m engine.cli.main init
Behind the scenes:
engine/installer/core.py:detect_ides()walks the project root for signature files (.claude/,.cursorrules,.windsurfrules, etc.).- For each detected IDE, it writes the right artifact:
- Claude Code → reuses existing
.claude-plugin/plugin.json - Cursor →
.cursorrules - Windsurf →
.windsurfrules - GitHub Copilot →
.github/copilot-instructions.md - Gemini CLI →
GEMINI.md - Codex →
AGENTS.md - And 11 more (see
engine/installer/core.pyfor the full list)
- Claude Code → reuses existing
- Validates Python engine import works.
- Runs
ux statsto print the manifest counts.
Output
{
"detected": ["claude-code", "cursor"],
"installs": [
{
"target": "claude-code",
"root": "/path/to/project",
"files_written": [],
"notes": ["Claude Code plugin already present"]
},
{
"target": "cursor",
"root": "/path/to/project",
"files_written": [".cursorrules"]
}
]
}
Manual invocation
If you've installed via pip, you can run this directly outside Claude Code:
ux init # detect + install for all
ux init --dry-run # show what would change without writing
ux install cursor # install for one specific IDE
ux install --root=/path/to/project cursor
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.
- 4d ago First seen · 90 lines · 42 tokens per session scan A 07efc7ff9a2b
ux-init is a command published in the GitHub repository Laith0003/ux-skill (65 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 740 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 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.
add-library
Kullanıcı "kütüphane ekle", "library ekle", "tasarım sistemi ekle", "design system ekle" dediğinde bu komutu uygula.
ds-remove
Kullanıcı "kütüphane kaldır", "library sil", "DS'i kaldır", "DS'i sil", "tasarım sistemini kaldır" dediğinde bu komutu uygula. Kullanıcı eski/yanlış eklenmiş bir DS'in cache'ini ve state'ini temizlemek ister.
design-system
Generate design tokens, theme configuration, or extract a design system from existing code or Figma files.
design-critique
UX heuristic review of Figma screens — evaluates against Nielsen's 10 heuristics, visual design quality, spacing, color, typography hierarchy, and interaction states.