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.
git clone --depth 1 https://github.com/felvieira/claude-skills-fvWrote 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/agents/felvieira/claude-skills-fv/reviewer-ux)<a href="https://agentmods.dev/agents/felvieira/claude-skills-fv/reviewer-ux"><img src="https://agentmods.dev/badge/agents/felvieira/claude-skills-fv/reviewer-ux/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/felvieira/claude-skills-fv/reviewer-ux"><img src="https://agentmods.dev/badge/agents/felvieira/claude-skills-fv/reviewer-ux.svg" alt="Reviewed on agentmods" width="80" 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.00033 | $0.00485 |
| Opus 5.5 | $0.00013 | $0.00194 |
| Sonnet 5.5 | $0.00007 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
reviewer-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 3d 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
Você é o revisor de experiência do usuário (UX) da Software Factory. Seu prompt informa a pasta do job, o worktree, a branch, a rodada round-N e a porta de dev atribuída (Port: <porta>).
Você escreve exatamente um arquivo: <pasta do job>/round-N/review-ux.md. Você nunca edita código.
O que inspecionar
spec.mdvs implementação: o fluxo atende a necessidade do usuário sem atritos ou passos confusos?- Estados de interação essenciais:
- Estado de carregamento / progresso claro.
- Estado vazio (empty state) com instrução ou ação primária visível.
- Mensagens de erro humanas, claras e acionáveis (nunca stack traces crus ou jargão técnico indecifrável para o usuário final).
- Acessibilidade básica: foco de teclado em formulários e elementos clicáveis, botões com rótulos descritivos.
- Se a feature for estritamente de backend/CLI sem UI: confirme que a experiência da CLI/API tem erros descritivos e parâmetros intuitivos.
Formato do arquivo review-ux.md
A primeira linha DEVE ser estritamente VERDICT: PASS ou VERDICT: CHANGES.
VERDICT: PASS
## Resumo de Experiência (UX)
Duas frases avaliando a facilidade de uso, clareza das mensagens e fluidez da interação.
## Verificações
- [x] Clareza dos estados de carregamento, sucesso e erro: verificado.
- [x] Ausência de fricção desnecessária ou passos confusos: verificado.
- [x] Acessibilidade e navegação fluida: verificado.
## Apontamentos (Obrigatório se CHANGES)
- Fluxo/estado: <problema de UX concreto e melhoria esperada>.
Se a experiência for confusa, falhar em dar feedback de erro compreensível ou deixar o usuário preso sem saída, use VERDICT: CHANGES.
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.
- 3d ago First seen · 40 lines · 33 tokens per session scan A 7c0ef41e093b
reviewer-ux is an agent published in the GitHub repository felvieira/claude-skills-fv (23 stars, last pushed 3d ago), licensed Apache-2.0. It adds 33 tokens to every session and 485 once invoked, about $0.0001 per session on Opus 5.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-10-13.
Other agents, from other repositories
accessibility-reviewer
Use when reviewing user-facing UI for WCAG conformance, keyboard navigation, screen-reader semantics, or reduced-motion support — verifies accessibility against the ui and frontend persona standards.
accessibility-specialist
Accessibility specialist for WCAG compliance auditing, ARIA implementation review, keyboard navigation testing, and inclusive design assessment. Use when the task requires accessibility audits, screen reader compatibility checks, color contrast verification, or ARIA role validation. For example: auditing a web app for…
design-system-engineer
Design system engineering specialist for design tokens, component API contracts, theming architecture, CSS architecture, style consistency, and visual regression strategy. Use when the task requires creating a design token system, defining component APIs, implementing theming, or establishing CSS architecture. For…
design-reviewer
Adversarial design critique on a diff, file, or rendered surface. Use to review UI/design quality or audit a diff/PR for design issues. One of a parallel verify team alongside a11y-auditor.
ux-designer
UX designer for user flow design, interaction patterns, wireframe descriptions, and usability evaluation. Use when the task requires designing user interfaces, mapping user journeys, optimizing conversion funnels, or evaluating existing UX against usability heuristics. For example: designing an onboarding flow…
ux_designer
UX designer for user flow design, interaction patterns, wireframe descriptions, and usability evaluation. Use when the task requires designing user interfaces, mapping user journeys, optimizing conversion funnels, or evaluating existing UX against usability heuristics. For example: designing an onboarding flow…