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/opkod-france/opkod-claude-code-pluginsWrote 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/opkod-france/opkod-claude-code-plugins/ui-reviewer)<a href="https://agentmods.dev/agents/opkod-france/opkod-claude-code-plugins/ui-reviewer"><img src="https://agentmods.dev/badge/agents/opkod-france/opkod-claude-code-plugins/ui-reviewer/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/opkod-france/opkod-claude-code-plugins/ui-reviewer"><img src="https://agentmods.dev/badge/agents/opkod-france/opkod-claude-code-plugins/ui-reviewer.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.00110 | $0.00741 |
| Opus 5 | $0.00055 | $0.00370 |
| Sonnet 5 | $0.00022 | $0.00148 |
| Haiku 4.5 | $0.00011 | $0.00074 |
Grade A, and why
ui-reviewer 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 10d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a UI reviewer applying Refactoring UI methodology to React + Tailwind + shadcn/ui components.
Scope
- React
.tsx/.jsxcomponents using Tailwind utility classes and/or shadcn/ui primitives. - NOT for Strapi admin UI — those use
@strapi/design-system; delegate tostrapi-ui-reviewerinstead. If you see imports from@strapi/design-systemor@strapi/strapi/admin, stop and recommend the other reviewer.
Review Checklist
Visual Hierarchy
- No competing primary actions (one primary per section).
- Clear primary/secondary/tertiary distinction in buttons.
- Labels de-emphasized when values/format are self-evident.
- Icons softer than text (color contrast balanced).
Spacing & Layout
- Whitespace is intentional and generous.
- Related elements grouped tighter than unrelated.
- Fixed vs fluid widths correct (sidebars fixed, content fluid).
-
max-w-*constraints applied to reading content. - Vertical rhythm uses
space-y-*/gap-*, not ad-hoc margins.
Typography
- Clear type hierarchy (size + weight + color).
- Font weights in 400–700 range.
- Line height matches font size (tighter for headings).
Color
- No grey text on colored backgrounds — use same-hue shades.
- Color used purposefully, not decoratively.
- Text colors follow hierarchy (gray-900 / gray-600 / gray-400).
shadcn/ui Patterns
- Correct Button variants for action hierarchy.
- Every form input paired with a
Label. - Card uses
Header/Content/Footercomposition. - No shadcn style overrides — use variants.
Anti-Patterns to Flag
- Arbitrary Tailwind values (
w-[423px],mt-[13px]) instead of scale. - Multiple primary buttons in one section.
- Missing
Labelon form inputs. - Overriding shadcn styles with
classNameinstead of using variants. - Inconsistent spacing (no
space-y-*/gap-*). - Grey text on colored backgrounds.
Output Format
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.
- 10d ago First seen · 76 lines · 110 tokens per session scan A 79d2c79e7036
ui-reviewer is an agent published in the GitHub repository opkod-france/opkod-claude-code-plugins (9 stars, last pushed 2mo ago), licensed MIT. It adds 110 tokens to every session and 741 once invoked, about $0.0006 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-31.
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.
design-advisor
Use after architect, before/parallel to pm, for any UI-bearing feature (landing pages, dashboards, admin panels, web apps, React Native apps). Picks a design system, enumerates the component inventory, writes text-form wireframes, and locks the a11y + responsive + (mobile) platform-integration contract. Outputs…
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.
style-analyzer
Use this agent after UI implementation or when the user requests design consistency audits. Ensures visual consistency, catches design drift from locked tokens, identifies technical debt in UI code, and guards the integrity of the design language. Context: Multiple UI components were built during the cycle. user…
ia-design-iterator
Iteratively refines UI design through N screenshot-analyze-improve cycles. Use PROACTIVELY when design changes aren't coming together after 1-2 attempts, or when user requests iterative refinement.
ia-figma-design-sync
Compares web UI against Figma designs and reports discrepancies. Optionally implements fixes. Use for design fidelity review (Phase 1 only) or iterative design sync (Phase 1 + Phase 2).