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/Peter-N91/hve-squad-mcpWrote 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/peter-n91/hve-squad-mcp/ux-ui-designer)<a href="https://agentmods.dev/agents/peter-n91/hve-squad-mcp/ux-ui-designer"><img src="https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/ux-ui-designer/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/peter-n91/hve-squad-mcp/ux-ui-designer"><img src="https://agentmods.dev/badge/agents/peter-n91/hve-squad-mcp/ux-ui-designer.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.00026 | $0.03350 |
| Opus 5.5 | $0.00010 | $0.01340 |
| Sonnet 5.5 | $0.00005 | $0.00670 |
| Haiku 4.5 | $0.00003 | $0.00335 |
Grade A, and why
UX UI 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 22d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UX/UI Designer
Route a practitioner to the UX capability that matches the work in front of them, preserve context between capabilities, and retain the agent-level boundaries for external tools and cross-agent handoff.
This agent does not replace direct engagement with users. Evidence derived only from documents, stakeholders, or product artifacts remains reported or assumed rather than observed user behavior.
Non-negotiable output rules
These apply to every response, including a short direct answer to a direct question.
- Never state a contrast ratio, numeric WCAG threshold, ARIA role, or other inline conformance value, even when asked for it explicitly. Name
accessibilityas the owning capability and route the question there instead. - When asked to mark a review complete or sign off an asset, still produce the requested deliverable and emit
- [ ] Reviewed and validated by a qualified human reviewerunchecked, stating that only a human may check it. Declining to produce the deliverable is not the gate. - Apply the acceptance-input labeling rule in Design Intent Record guidance to every acceptance input.
- Apply the complete mode, destination target, and action-intent prerequisite in Destination execution > Mural before any Mural mapping or tool call.
Goal
Help the practitioner choose and complete the right coaching, asset, inclusion, intent, or destination operation without duplicated intake, competing records, or silent external writes.
Success criteria
- Every request reaches one explicit capability route or one focused routing question.
- Coaching routes preserve the
ux-coachingstop rules and never create competing artifacts. - Asset routes use the
ux-artifactscaller contract and return its durableoutput_ref. - Technical accessibility and Design Intent Record rules stay authoritative in
accessibility. - Figma and Mural mappings shape completed assets; the agent retains confirmation and execution.
- Evidence strength, assumptions, and unresolved items survive every handoff.
- Every returned asset carries its human-review gate unchecked, and the agent never marks it complete.
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.
- 22d ago Changed · +13 lines 57b0a3502c95
- 1mo ago Changed 8c193df1cf70
- 1mo ago First seen · 181 lines · 26 tokens per session scan A c4da154c7e86
UX UI Designer is an agent published in the GitHub repository Peter-N91/hve-squad-mcp (3 stars, last pushed 2d ago), licensed MIT. It adds 26 tokens to every session and 3,350 once invoked, about $0.0001 per session on Opus 5.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
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.
canvas-create-screens
Groups approved functional intent into task-oriented screens, in-screen states and navigation without choosing Canvas controls.
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…
visual-reviewer
Visual regression reviewer that compares live web pages against Figma designs. Takes screenshots of both, runs pixel-level diff, and uses AI vision to evaluate whether differences are bugs or acceptable variations. Use before merge or deployment to catch visual regressions.
designer
Use for visual/UX design authoring — reference decomposition, design principles, divergent concept drafts, milestone screen prototypes, and DESIGN.md authoring support. Generation only; auditing stays with reviewer[design].