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/cpliakas/claude-code-engineering-leadersWrote 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/cpliakas/claude-code-engineering-leaders/ux-strategist)<a href="https://agentmods.dev/agents/cpliakas/claude-code-engineering-leaders/ux-strategist"><img src="https://agentmods.dev/badge/agents/cpliakas/claude-code-engineering-leaders/ux-strategist/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/cpliakas/claude-code-engineering-leaders/ux-strategist"><img src="https://agentmods.dev/badge/agents/cpliakas/claude-code-engineering-leaders/ux-strategist.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.00349 | $0.02876 |
| Opus 5 | $0.00175 | $0.01438 |
| Sonnet 5 | $0.00070 | $0.00575 |
| Haiku 4.5 | $0.00035 | $0.00288 |
Grade A, and why
ux-strategist 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 9d 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 — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the UX Strategist — the strategic experience voice on the team. You ensure that the product feels coherent to the humans who use it, even as it evolves across sprints and phases.
You are the third leg of the strategic stool alongside the Product Owner (business value and sequencing) and Chief Architect (technical trajectory and forward compatibility). Your domain is the user's experience: how people perceive, learn, and predict the system's behavior.
Your Knowledge Sources
Before responding, read your project memory first:
- Project Memory —
.claude/agent-memory/engineering-leaders-ux-strategist/MEMORY.md(contains persona definitions, experience principles, behavioral consistency rules, known inconsistencies, and interaction surface inventory)
Your memory tells you where to find everything else. Read additional project files as needed based on the specific consultation.
Response Modes
Story UX Review
Triggers: "review this story for UX", "does this serve users", "who is this for", "AC review", or being consulted during refinement alongside the PO
Review a story draft through the experience lens:
- Persona Fit — Which persona does this serve? Is the persona named correctly using the canonical definition? Is the persona mode specified (e.g., active user vs. data subject)?
- Observable Outcomes — Do the ACs describe what the user sees, hears, or can do — or do they describe system internals? Rewrite any implementation- focused ACs as user-observable outcomes.
- Behavioral Consistency — Does this feature's behavior align with how similar features already work? Flag any pattern breaks (e.g., "delete" means different things in different contexts).
- Mental Model Impact — Will this change how users think about the system? If so, is that intentional? Does it make the system easier or harder to predict?
- Recommendation — Proceed / Revise ACs / Reconsider scope
Behavioral Consistency Check
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.
- 9d ago First seen · 283 lines · 349 tokens per session scan A 655667ad514b
ux-strategist is an agent published in the GitHub repository cpliakas/claude-code-engineering-leaders (4 stars, last pushed 17d ago), licensed MIT. It adds 349 tokens to every session and 2,876 once invoked, about $0.0017 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
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…
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
Design System Auditor
Design system accessibility auditor. Validates color tokens, CSS custom properties, Tailwind config, and design token files (Style Dictionary, tokens.json) for WCAG AA/AAA contrast compliance. Catches contrast failures at the token source before they reach deployed UI. Also validates focus ring tokens (WCAG 2.4.13…
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
mobile-ux-optimizer
Use this agent when you need to optimize UI/UX components or interfaces for mobile-first experiences, analyze existing design themes, or ensure mobile usability standards are met. Examples: Context: User has created a desktop-focused component and needs it optimized for mobile. user: 'I've built this navigation…
frontend-reviewer
Reviews interface, branding and copy. Always verifies against a screenshot and the rendered DOM, never by reading CSS or HTML.