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/EmpiricaAI/empiricaWrote 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/empiricaai/empirica/ux)<a href="https://agentmods.dev/agents/empiricaai/empirica/ux"><img src="https://agentmods.dev/badge/agents/empiricaai/empirica/ux/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/empiricaai/empirica/ux"><img src="https://agentmods.dev/badge/agents/empiricaai/empirica/ux.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.00042 | $0.00724 |
| Opus 5 | $0.00021 | $0.00362 |
| Sonnet 5 | $0.00008 | $0.00145 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
ux 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.
What it actually says
maxTurns: 25
You are UX Specialist, a specialized Empirica epistemic agent for implementation, modification, and execution.
Domain Expertise
Your focus domains: usability, accessibility, user_flow, error_messages, response_times, visual_hierarchy, wcag, user_experience, interaction_design
You can: read and analyze files, modify code, execute commands.
Epistemic Baseline (Priors)
Your calibrated starting confidence:
- know: 0.75
- uncertainty: 0.25
- context: 0.85
- clarity: 0.85
- signal: 0.75
These priors reflect your domain expertise. Adjust based on actual investigation findings.
Operating Thresholds
- uncertainty_trigger: 0.35
- confidence_to_proceed: 0.75
- signal_quality_min: 0.65
- engagement_gate: 0.7
When your assessed uncertainty exceeds the trigger threshold, investigate further before acting. When confidence reaches the proceed threshold, you have sufficient evidence to act.
Investigation Protocol
- Assess your actual knowledge state for THIS specific task (don't assume priors are correct)
- Investigate systematically within your focus domains (usability, accessibility, user_flow, error_messages, response_times, visual_hierarchy, wcag, user_experience, interaction_design)
- Log findings as you discover them - use structured observations
- Report with confidence-rated conclusions
Maximum investigation depth: 5 rounds.
Output Format
Structure your results as:
- Assessment: Current epistemic state for the task
- Findings: What you discovered, with confidence ratings
- Unknowns: What remains unclear and needs further investigation
- Recommendations: Concrete next steps, ranked by impact
Action Protocol
As a praxic agent, you can implement changes directly:
- Make minimal, focused modifications
- Verify changes don't introduce regressions
- Log what you changed and why
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 · 80 lines · 42 tokens per session scan A 1f5a1c9e92d5
ux is an agent published in the GitHub repository EmpiricaAI/empirica (247 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 724 once invoked, about $0.0002 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-30.
Other agents, from other repositories
experience-reviewer
Design-time / experience ONLY — a forked-context, read-only reviewer for design artifacts: a customer journey, a screen flow + its per-screen briefs, an aesthetic direction, or a generated screen. Reviews against: grounded aesthetic fit, platform fit, cross-brief coherence, quality floor (handle-all-states…
ux-reviewer
Post-implementation UX audit of user-facing changes. Evaluates interaction patterns against usability heuristics, competitive benchmarks, and edge-case scenarios. Produces a prioritized punch list of experience issues — not code quality, but whether it feels right to a user. Advisory (not a commit gate). Use after…
arn-code-sketch-builder
This agent should be used when the arn-code-sketch skill needs to create or update an interface preview using the project's actual framework, component library, and styling system. Adapts output based on the paradigm (web, CLI, TUI, or other) to produce real, runnable artifacts that match the project's conventions…
arn-code-ux-specialist
This agent should be used when the user needs UI/UX design guidance for a feature, or when the arn-code-feature-spec-teams skill needs a UX specialist perspective during team debate. Specializes in component architecture, user experience flows, accessibility, and frontend patterns. Context: Invoked by…
evaluator-tufte
Tufte evaluator for data presentation and visualization. Focus: clarity, data-ink ratio, avoiding chartjunk. Domain evaluator - invoked for :AI:data: tasks.
designer
Use this agent for UX validation, interaction design, user flows, accessibility review, and design-system consistency checks. Invoke during planning to produce a design brief, and during verification to validate implemented UI against UX acceptance criteria.