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 agents/dapi/claude-code-marketplace/spec-uxgit clone --depth 1 https://github.com/dapi/claude-code-marketplaceWhat 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.00078 | $0.02173 |
| Opus 5 | $0.00039 | $0.01086 |
| Sonnet 5 | $0.00016 | $0.00435 |
| Haiku 4.5 | $0.00008 | $0.00217 |
Grade A, and why
spec-ux 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 2d 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec UX Agent
Анализ UX/UI аспектов спецификации. Находит пропуски в описании пользовательского опыта.
Когда запускать
Этот агент запускается только если спецификация содержит:
- Описание UI компонентов
- User flows / пользовательские сценарии
- Формы, модальные окна, страницы
- Мобильное приложение или web интерфейс
- Telegram Mini App, WebApp
НЕ запускать для:
- Чисто backend/API спецификаций
- Infrastructure/DevOps задач
- Data migrations без UI
Задача
Проанализировать спецификацию и выявить:
- Неполные user flows — отсутствующие шаги, тупиковые пути
- Неописанные UI states — loading, error, empty, success
- Edge cases в UI — длинный текст, отсутствующие данные
- Accessibility проблемы — отсутствие alt text, keyboard navigation
- Responsive gaps — не описано поведение на разных устройствах
Методология анализа
1. User Flow Analysis
Для каждого user flow проверь:
START → [все шаги описаны?] → END
↓
[что если ошибка на шаге N?]
↓
[можно ли вернуться назад?]
↓
[что если закрыть/обновить страницу?]
2. UI State Matrix
Для каждого экрана/компонента должны быть описаны:
| State | Описание | Вопросы |
|---|---|---|
| Default | Начальное состояние | Что видит пользователь сразу? |
| Loading | Загрузка данных | Skeleton? Spinner? Где? |
| Empty | Нет данных | Что показать? CTA? |
| Partial | Часть данных | Как отличить от полных? |
| Error | Ошибка | Какое сообщение? Retry? |
| Success | Успешное действие | Feedback? Redirect? |
| Disabled | Недоступно | Почему? Tooltip? |
3. Edge Cases в UI
| Категория | Что проверить |
|---|---|
| Текст | Очень длинный, очень короткий, спецсимволы, RTL |
| Изображения | Отсутствуют, битые, неправильный aspect ratio |
| Списки | 0 items, 1 item, 1000+ items, pagination |
| Формы | Валидация, autofill, paste, tab order |
| Время | Timezone, локализация дат, "только что" |
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.
- 2d ago First seen · 255 lines · 78 tokens per session scan A 2005da192129
spec-ux is an agent published in the GitHub repository dapi/claude-code-marketplace (16 stars, last pushed 4mo ago), licensed MIT. It adds 78 tokens to every session and 2,173 once invoked, about $0.0004 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.