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-statsgit 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-stats)<a href="https://agentmods.dev/commands/laith0003/ux-skill/ux-stats"><img src="https://agentmods.dev/badge/commands/laith0003/ux-skill/ux-stats.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.00043 | $0.00443 |
| Opus 5 | $0.00022 | $0.00221 |
| Sonnet 5 | $0.00009 | $0.00089 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
ux-stats 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.
What it actually says
/ux-stats — show the data inventory
One command. One snapshot.
Prints the version, then the count of entries in each of the 11 data manifests:
{
"version": "2.0.0-alpha.1",
"counts": {
"styles": 84,
"palettes": 176,
"type-pairs": 70,
"components": 148,
"industries": 170,
"chart-types": 35,
"tech-stacks": 25,
"ux-guidelines": 112,
"motion-presets": 57,
"anti-patterns": 35,
"brands": 72
}
}
When to use
- Verify the install — confirm the data files are present and reasonable counts.
- Audit before a release — check no manifest has dropped entries.
- Quick sanity check after upgrading via
pip install --upgrade uxskill.
How it runs
python3 -m engine.cli.main stats
Behind the scenes this calls engine.data_loader.stats() which loads each
manifest, reads the _meta.entries count and the actual entry list length,
and returns the dictionary above.
Manual invocation
ux stats # pretty (rich) output by default
ux --no-pretty stats # raw JSON, pipe-friendly
ux stats | jq '.counts' # extract just counts
Errors
{"missing": true}in a count → the JSON file isn't present yet. Runpip install --upgrade uxskillor check the install path.- Counts of 0 → the JSON file exists but is empty. Open an issue at https://github.com/Laith0003/ux-skill/issues.
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 · 61 lines · 43 tokens per session scan A 6981acbb64ea
ux-stats is a command published in the GitHub repository Laith0003/ux-skill (66 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 443 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.
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.