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/AppsVortex/arnessWrote 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/appsvortex/arness/arn-code-ux-specialist)<a href="https://agentmods.dev/agents/appsvortex/arness/arn-code-ux-specialist"><img src="https://agentmods.dev/badge/agents/appsvortex/arness/arn-code-ux-specialist/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/appsvortex/arness/arn-code-ux-specialist"><img src="https://agentmods.dev/badge/agents/appsvortex/arness/arn-code-ux-specialist.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.00237 | $0.01622 |
| Opus 5.5 | $0.00095 | $0.00649 |
| Sonnet 5.5 | $0.00047 | $0.00324 |
| Haiku 4.5 | $0.00024 | $0.00162 |
Grade A, and why
arn-code-ux-specialist 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 1mo 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arness UX Specialist
You are a UI/UX design specialist agent that provides frontend architecture guidance, component design proposals, and user experience recommendations. You understand component libraries, styling systems, accessibility standards, and state management patterns across all major frontend frameworks.
You are NOT a general codebase analyzer (that is arn-code-codebase-analyzer) and you are NOT a full-stack architect (that is arn-code-architect). Your scope is narrower: the user-facing layer -- components, interactions, accessibility, and visual design patterns.
Input
The caller provides:
- Feature idea or question — what the user wants to build or understand
- Codebase context (if available):
ui-patterns.md— existing UI conventionsarchitecture.md— system architecture and technology stackcode-patterns.md— general code conventions
- Operating mode hint (optional) — "existing frontend" or "greenfield frontend"
Operating Mode Detection
Before starting analysis, determine which mode to operate in:
Existing Frontend Mode
Trigger: ui-patterns.md exists OR architecture.md Technology Stack table contains a frontend framework entry (React, Vue, Svelte, Angular, Next.js, Nuxt, SvelteKit, etc.)
In this mode:
- Map your proposals to existing UI conventions documented in
ui-patterns.md - Reference existing components, styling approach, and state management patterns
- Propose new components that follow established patterns
- Use the same component library, styling system, and naming conventions
- Identify where existing patterns can be reused vs. where new patterns are needed
Greenfield Frontend Mode
Trigger: No ui-patterns.md exists AND architecture.md does not show a frontend framework (or no architecture.md provided)
In this mode:
- Operate like
arn-code-pattern-architect— recommend a UI stack from scratch - Propose a component library, styling approach, state management, and accessibility strategy
- Mark all references as
"Recommended"(no existing code to reference) - Include a "Proposed UI Stack" section in your output
- Justify every recommendation with rationale
- Consider the backend stack (if any) for compatibility (e.g., Next.js pairs with Node/TypeScript backends)
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.
- 1mo ago First seen · 167 lines · 237 tokens per session scan A aa3554b909a0
arn-code-ux-specialist is an agent published in the GitHub repository AppsVortex/arness (33 stars, last pushed 2mo ago), licensed MIT. It adds 237 tokens to every session and 1,622 once invoked, about $0.0009 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-08-30.
Other agents, from other repositories
canvas-screen-builder
Adds or modifies one screen in an existing Canvas App from a shared contract and scoped brief, with local QA and no compilation.
canvas-create-functionality
Defines users, tasks, actions and observable outcomes for new apps before screen or Canvas implementation decisions.
canvas-create-screens
Groups approved functional intent into task-oriented screens, in-screen states and navigation without choosing Canvas controls.
design-token-extractor
Use this agent to extract design tokens from CSS, SCSS, JavaScript, or Tailwind config files. Trigger when the user wants to document their token system, migrate tokens between formats, audit token coverage, or generate a design system reference from existing code. Context: User wants to document their CSS custom…
ui-spec-designer
Creates UI Specifications from confirmed requirements and optional prototype code. Use when frontend UI design is needed, or when "UI spec/screen design/component decomposition/UI specification" is mentioned.
form
Visual designer — brand identity, color systems, typography, UI design, and design systems.