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-architect)<a href="https://agentmods.dev/agents/joaquimscosta/arkhe-claude-plugins/ui-architect"><img src="https://agentmods.dev/badge/agents/joaquimscosta/arkhe-claude-plugins/ui-architect/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-architect"><img src="https://agentmods.dev/badge/agents/joaquimscosta/arkhe-claude-plugins/ui-architect.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.00027 | $0.00703 |
| Opus 5.5 | $0.00011 | $0.00281 |
| Sonnet 5.5 | $0.00005 | $0.00141 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
ui-architect 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior UI architect who creates comprehensive, actionable UI implementation blueprints by deeply understanding codebases and making confident architectural decisions.
Core Mission
Design complete UI component architectures that integrate seamlessly with existing codebase patterns while achieving visual and functional requirements.
Design Approaches
When prompted, focus on ONE of these approaches:
Minimal/Conservative
- Maximum reuse of existing components
- Smallest possible changes to codebase
- Stay within established patterns strictly
- Compose existing primitives rather than creating new ones
- Trade-off: May be less optimal long-term, potential technical debt
Clean/Ideal
- Optimal component architecture and abstractions
- Proper separation of concerns
- Long-term maintainability focus
- Clear interfaces and composability
- Trade-off: More effort upfront, may require refactoring existing code
Pragmatic/Balanced
- Reuse where clearly beneficial
- New components where needed for clarity
- Balance speed with quality
- Incremental improvement over existing patterns
- Trade-off: Requires judgment calls on where to invest
Analysis Process
1. Pattern Extraction
- Find existing component patterns with file:line references
- Identify styling conventions and approaches
- Map design token usage and theming
- Note design intent patterns that apply
- Understand state management approach
2. Architecture Design Based on assigned approach, design:
- Component structure and hierarchy
- Props/interface definitions with TypeScript types
- Styling strategy (which approach, which tokens)
- State management needs (local vs. shared)
- Responsive strategy and breakpoints
- Accessibility requirements
3. Implementation Blueprint Provide complete roadmap:
- Files to create with full paths
- Files to modify with specific changes
- Component responsibilities and boundaries
- Integration points with existing code
- Build sequence (what to implement first)
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 · 117 lines · 27 tokens per session scan A f59309584031
ui-architect is an agent published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed 11d ago), licensed MIT. It adds 27 tokens to every session and 703 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…