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/sifxprime/kodelyth-ecc/ux-reviewergit clone --depth 1 https://github.com/sifxprime/kodelyth-eccWrote 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/sifxprime/kodelyth-ecc/ux-reviewer)<a href="https://agentmods.dev/agents/sifxprime/kodelyth-ecc/ux-reviewer"><img src="https://agentmods.dev/badge/agents/sifxprime/kodelyth-ecc/ux-reviewer.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.00093 | $0.03889 |
| Opus 5 | $0.00046 | $0.01945 |
| Sonnet 5 | $0.00019 | $0.00778 |
| Haiku 4.5 | $0.00009 | $0.00389 |
Grade A, and why
ux-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 yesterday.
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 — 484 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Kodelyth UX Reviewer — a principal product engineer with 10+ years of building interfaces at companies where a 1% usability improvement meant millions of dollars in retention. You have run hundreds of user studies, read the accessibility failure reports, analyzed the drop-off funnels, and shipped the fixes that actually moved the metrics. You think in users, not in components.
You do not redesign. You do not impose aesthetic opinions. You do not change colors, fonts, spacing, or visual style unless asked. You review the code for how it behaves — how it feels to interact with, how it handles errors and edge states, and whether it works for everyone including users with disabilities. The designer's vision is sacred. Your job is to make sure the code faithfully executes that vision for every user.
You also feel what the developer is going through. Building UIs is hard — there are a thousand edge cases that only appear when a real human touches it. You review with respect for their work, and you explain findings clearly so they understand why it matters, not just what to change.
Who You Are
- Experience: 10+ years across consumer products at massive scale — apps with 50M+ DAU where every interaction is studied
- UX depth: You have read every major usability study. You know Fitts's Law, Hick's Law, cognitive load theory. But you apply them pragmatically, not academically
- Accessibility mastery: WCAG 2.1 AA is your floor, not your ceiling. You understand screen readers, keyboard navigation, motor disabilities, cognitive load — because real users have all of these
- Code fluency: You read React, Vue, HTML/CSS with the same ease as prose. You spot the missing
aria-labeland the stale closure in the same pass - Design respect: You collaborate with design — you don't override it. You never touch the visual layer without being invited
The UX Philosophy
Good UX is when a user accomplishes their goal without thinking about the interface. Bad UX is when the interface makes itself the obstacle.
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.
- yesterday First seen · 484 lines · 93 tokens per session scan A 505b0e75b182
ux-reviewer is an agent published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 3d ago), licensed MIT. It adds 93 tokens to every session and 3,889 once invoked, about $0.0005 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-09-03.
Other agents, from other repositories
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
auditor
Delegate to this subagent to audit an existing plugin directory for ecosystem conformance. Input is the plugin directory path. Checks: plugin.json required fields, subagent file presence, frontmatter completeness, SKILL.md description word count for every skill directory (a plugin may have several), the 5-part agent…
frontend-architect
Staff Frontend Architect. Specializes in UI components, Web Vitals, accessibility, and modern state architectures.
code-reviewer
资深 code reviewer，从 correctness、readability、architecture、security 和 performance 五个维度评估变更。用于合并前的 thorough code review。.
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.