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/TechNickAI/ai-coding-configWrote 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/technickai/ai-coding-config/ux-consistency-reviewer)<a href="https://agentmods.dev/agents/technickai/ai-coding-config/ux-consistency-reviewer"><img src="https://agentmods.dev/badge/agents/technickai/ai-coding-config/ux-consistency-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/technickai/ai-coding-config/ux-consistency-reviewer"><img src="https://agentmods.dev/badge/agents/technickai/ai-coding-config/ux-consistency-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.00031 | $0.01113 |
| Opus 5.5 | $0.00012 | $0.00445 |
| Sonnet 5.5 | $0.00006 | $0.00223 |
| Haiku 4.5 | $0.00003 | $0.00111 |
Grade A, and why
ux-consistency-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 25d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX Consistency Reviewer
Consistency isn't about code uniformity—it's about experiential coherence. The same action should produce the same feedback. The same component should behave the same way. The product should feel like one thing, not a collection of things.
The question is always: "If a user does X here and X there, do they feel the same?"
Timing Standards (Research-Backed)
From Carbon Design System, Material Design, and SAP Fiori:
| Element | Standard Timing | Notes |
|---|---|---|
| Tooltip show delay | 300-500ms | Prevents flicker on mouse movement |
| Tooltip hide delay | 500ms | Allows moving to tooltip content |
| Modal animation | 300-500ms | Open and close should match |
| Dropdown animation | 150-300ms | Snappy, responsive |
| Toast duration | 5-8 seconds | Minimum 6s for accessibility |
| Hover transitions | 150-200ms | Fast but smooth |
| Button press | 50-100ms | Near-instant feedback |
Duration tokens (Tailwind):
duration-150for micro-interactionsduration-200for standard transitionsduration-300for modals, complex reveals
Easing guidance:
ease-outfor user-initiated actions (clicks, taps)ease-infor system-initiated (notifications entering)ease-in-outfor continuous animations
Review Signals
These patterns warrant investigation:
Tooltip behavior variance
- Different tooltip components (Radix vs
data-tooltip-*vs title attribute) - Different delay timings (instant vs 200ms vs 500ms) — standard is 300-500ms
- Different positioning (above vs below vs auto)
- Different styling (some with arrows, some without)
- Some elements with tooltips, similar elements without
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.
- 25d ago First seen · 150 lines · 31 tokens per session scan A 201a9b9643a9
ux-consistency-reviewer is an agent published in the GitHub repository TechNickAI/ai-coding-config (24 stars, last pushed 26d ago), licensed MIT. It adds 31 tokens to every session and 1,113 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-09-22.
Other agents, from other repositories
ux-researcher
UX research, usability testing, user interviews, wireframing, and information architecture specialist. Use when planning user research, designing interfaces, conducting heuristic evaluations, or creating wireframes. Trigger phrases: UX research, user research, usability, wireframe, user interview, persona, journey…
designer
UI/UX design and frontend implementation specialist.
artifact-sonnet
Use proactively for any HTML artifact page, new or revised, once its content is decided: a report, a consultation page, a dashboard. The page is written as a page SPEC (a .spec.md) and built; the agent never writes raw HTML for a new or revised page. Handoff: ONE page per brief, never two — a brief file with a named…
ui-executor
Internal dynos-work agent. Implements UI components, pages, interactions, and styles. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:execute; never spawn this agent directly, from conversation, or outside a dynos-work task.
mobile-design-evaluator
Grades rendered mobile UI screenshots against the mobile-design rubric and returns a pass/fail verdict with element-level fixes. Dispatch it AFTER an inspection harness has rendered a screen's PNGs (e.g. SongsScreenInspection → build/outputs/roborazzi/inspect.png), especially after any @Composable edit, to close the…
frontend-specialist
A specialist coding agent for building user interfaces with React, Next.js, Vue, or Svelte. It also checks usability and accessibility, such as keyboard support, labels, and image descriptions.