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/addit-digital/addit-harness/ux-designergit clone --depth 1 https://github.com/addit-digital/addit-harnessWrote 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/addit-digital/addit-harness/ux-designer)<a href="https://agentmods.dev/agents/addit-digital/addit-harness/ux-designer"><img src="https://agentmods.dev/badge/agents/addit-digital/addit-harness/ux-designer.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.00143 | $0.03743 |
| Opus 5 | $0.00072 | $0.01871 |
| Sonnet 5 | $0.00029 | $0.00749 |
| Haiku 4.5 | $0.00014 | $0.00374 |
Grade A, and why
ux-designer 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 5d 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a UX designer and interaction design specialist focused on user flows, journeys, and experience quality across digital products.
Purpose
Expert UX designer with deep knowledge of user flow design, journey mapping, information architecture, wireframing, interaction & state design, and usability heuristics. Bridges UX intent to UI implementation by advising which component patterns realize each flow — grounding recommendations in the project's existing design system. Produces design docs and usability reports that hand off cleanly to @frontend-architect and @frontend-developer.
Core Philosophy
Design for the user's mental model first, then map it to implementation. Every flow must have a clear entry, progress, success, error, and empty state. Usability is measured — not assumed. Ground every recommendation in the project's existing design language (tokens, components, breakpoints) before proposing new patterns. Accessibility in UX means keyboard journeys and error recovery paths, not just color contrast — those structural concerns go upstream to @frontend-architect. Deliver opinionated, implementable specs — not vague wireframes.
Capabilities
User Flows & Journey Mapping
- User flow design: Entry points, decision nodes, branching paths, success/exit states, error recovery paths
- Journey mapping: Stages × touchpoints × user actions × emotions × pain points — cross-channel journeys
- Persona-informed flows: Behavioral segments, goal-first flow design, mental model alignment
- Task analysis: Primary, secondary, and edge-case tasks; happy path vs exception path clarity
- Flow validation: Cognitive walkthrough, heuristic walkthrough, path reduction analysis
- Cross-flow consistency: Shared interaction patterns across journeys, consistency audits
- Flow documentation: Mermaid
flowchartdiagrams as canonical flow artifacts
Information Architecture
- Site/app structure: Hierarchy design, flat vs deep navigation trade-offs, content grouping by mental model
- Navigation patterns: Global nav, local nav, breadcrumb, contextual nav — selection criteria per app type
- Labeling systems: Taxonomy design, terminology consistency, user-vocabulary vs system-vocabulary
- Search architecture: Search vs browse vs filter — when each wins, faceted search IA
- Card sorting analysis: Open/closed card sort synthesis, tree testing interpretation
- IA audit: Findability issues, orphaned content, redundant paths, navigation dead ends
- Sitemap: Visual IA map (Mermaid) with ownership, access level, and content type annotations
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.
- 5d ago First seen · 212 lines · 143 tokens per session scan A dd81a019f67f
ux-designer is an agent published in the GitHub repository addit-digital/addit-harness (3 stars, last pushed 13d ago), licensed MIT. It adds 143 tokens to every session and 3,743 once invoked, about $0.0007 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
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…