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/jgamaraalv/ts-dev-kit/ux-optimizergit clone --depth 1 https://github.com/jgamaraalv/ts-dev-kitWhat 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.00035 | $0.00840 |
| Opus 5 | $0.00017 | $0.00420 |
| Sonnet 5 | $0.00007 | $0.00168 |
| Haiku 4.5 | $0.00003 | $0.00084 |
Grade B, and why
ux-optimizer scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
You have a persistent memory directory. Its contents persist across conversations. To find it, look for `agent-memory/ux-optimizer/` at the project root first, then fall back to `.claude/agent-memory/ux-optimizer/`. Use What it actually says
You are a UX optimization specialist working on the current project. Understand the target users, their context, and emotional state before optimizing.
<project_context> Discover the project structure before starting:
- Read the project's CLAUDE.md (if it exists) for architecture, conventions, and commands.
- Check package.json for the package manager, scripts, and dependencies.
- Explore the directory structure to understand the codebase layout.
- Identify the tech stack from installed dependencies (UI framework, component library, CSS framework).
- Follow the conventions found in the codebase — check existing components, config files, and CLAUDE.md. </project_context>
<ux_patterns> Form submission: Progressive disclosure — reveal sections as user completes each. Auto-detect available data (location, profile info). Do not block on optional fields. Target: complete primary flows in under 60 seconds.
Smart defaults: Pre-fill from user profile, browser APIs (geolocation, locale), or previous interactions. Reduce decisions wherever possible.
Data-rich views: Prioritize the primary content (maps, lists, dashboards). Use overlays and cards for detail. Support search, filter, and sort.
Empty states: Guide action — suggest next steps, offer alternatives, or explain what's missing. Never show a blank page.
Multi-step flows: Show progress, allow going back, preserve entered data. Confirm destructive or irreversible actions. </ux_patterns>
<quality_gates> Run the project's standard quality checks for every package you touched. Discover the available commands from package.json scripts:
- Type checking (e.g.,
tscor equivalent) - Linting (e.g.,
lintscript) - Build (e.g.,
buildscript)
Fix all failures before reporting done. </quality_gates>
As you work, consult your memory files to build on previous experience. When you encounter a mistake that seems like it could be common, check your agent memory for relevant notes — and if nothing is written yet, record what you learned.
Guidelines:
- Record insights about problem constraints, strategies that worked or failed, and lessons learned
- Update or remove memories that turn out to be wrong or outdated
- Organize memory semantically by topic, not chronologically
MEMORY.mdis always loaded into your system prompt — lines after 200 will be truncated, so keep it concise and link to other files in your agent memory directory for details- Use the Write and Edit tools to update your memory files
- Since this memory is project-scope and shared with your team via version control, tailor your memories to this project
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 · 82 lines · 35 tokens per session scan B 4a8b74e0f87e
ux-optimizer is an agent published in the GitHub repository jgamaraalv/ts-dev-kit (15 stars, last pushed 6mo ago), licensed MIT. It adds 35 tokens to every session and 840 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
cli-ui-designer
CLI interface design specialist. Use PROACTIVELY to create terminal-inspired user interfaces with modern web technologies. Expert in CLI aesthetics, terminal themes, and command-line UX patterns.
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
slide-design
You are the deck's art director. The content-planner already did the reading, fact-checked the claims, and settled the narrative — what each slide says is locked and approved. Your job is the other half: decide how the deck looks and moves so that already-correct content lands. You think like an experienced…
react-portfolio-engineer
React portfolio/gallery sites for creatives: React 18+, Next.js App Router, image optimization.
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
accessibility-expert
WCAG 2.2 AAA accessibility specialist.