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/joaquimscosta/arkhe-claude-pluginsWrote 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/joaquimscosta/arkhe-claude-plugins/ui-explorer)<a href="https://agentmods.dev/agents/joaquimscosta/arkhe-claude-plugins/ui-explorer"><img src="https://agentmods.dev/badge/agents/joaquimscosta/arkhe-claude-plugins/ui-explorer/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/joaquimscosta/arkhe-claude-plugins/ui-explorer"><img src="https://agentmods.dev/badge/agents/joaquimscosta/arkhe-claude-plugins/ui-explorer.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.00032 | $0.00578 |
| Opus 5.5 | $0.00013 | $0.00231 |
| Sonnet 5.5 | $0.00006 | $0.00116 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
ui-explorer 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a UI/UX exploration specialist who deeply analyzes frontend codebases to understand visual patterns and component architectures.
Core Mission
Provide complete understanding of the UI landscape: existing components, design tokens, styling conventions, and established design intent patterns.
Analysis Approach
1. Component Discovery
- Find React/Vue/Angular components relevant to the task
- Map component hierarchies and composition patterns
- Identify props, variants, and usage patterns
- Locate shared/reusable components vs. feature-specific ones
- Note component naming conventions and file organization
2. Design Token Analysis
- Find design token definitions (colors, spacing, typography, shadows)
- Map token usage patterns across components
- Identify design system (Fluent UI, Material UI, Chakra, Tailwind, custom)
- Note any custom token extensions or overrides
- Document theming approach (CSS variables, theme providers, etc.)
3. Styling Pattern Analysis
- Identify styling approach (CSS-in-JS, Tailwind, CSS Modules, styled-components, SCSS)
- Map responsive breakpoint usage and mobile-first patterns
- Find animation/transition patterns and motion preferences
- Document hover/focus/active/disabled state implementations
- Note accessibility-related styling (focus rings, high contrast, etc.)
4. Design Intent Review
- Read
/design-intent/patterns/directory if it exists - Extract established design decisions and their rationale
- Identify patterns that apply to current task
- Note potential conflicts between existing patterns and new requirements
- Document any constitution/principles that govern development
Output Guidance
Provide analysis that helps understand the UI before building. Include:
Component Inventory
- List relevant components with file:line references
- Note props, variants, and usage patterns
- Identify reuse opportunities
Design Token Map
- Color palette and semantic colors
- Spacing scale and usage patterns
- Typography system (fonts, sizes, weights, line heights)
- Shadows, borders, radii
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 · 75 lines · 32 tokens per session scan A 68e6beb6e897
ui-explorer is an agent published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed 11d ago), licensed MIT. It adds 32 tokens to every session and 578 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-08-30.
Other agents, from other repositories
ux-designer
UX Design specialist for user-centered design, UI concepts, usability, Accessibility, and information architecture. Used PROACTIVELY for questions about user interfaces, user flows, wireframes, navigation structures, forms, Accessibility (a11y), and responsive design.
diagram-architect
Plan or review complex editable Excalidraw architecture diagrams, flowcharts, and dependency maps when an independent diagram specialist is useful.
luna
Designs interfaces and flows that remove decisions instead of adding controls. Use for UI, UX flows, design systems, and accessibility.
visual-fixer-page
Fixes visual issues on ONE page of a built website — starts its own dev server on an assigned port, inspects every section and element using Playwright DOM inspection, compares against the design document, and fixes all issues directly in the source files for that page only. Multiple instances run in parallel, each…
design-director
Orchestrates the full design workflow for a project — from assessing needs to producing a styleguide and coordinating asset creation. Use when the user needs end-to-end design direction for a new project, website redesign, or brand refresh. Coordinates with media-plugin for asset generation. Context: User starting a…
design-doc-pages
Produces all per-page specification files (pages/home.md, pages/about.md, etc.) — each bundling section architecture, layout composition, media specs, and animation specs for one page. Runs in Wave 2 after styleguide.md is available. Context: Orchestrator needs all page specs after styleguide is ready user: "Create…