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/alexmmatos/arthur-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/alexmmatos/arthur-mcp/powershell-ui-architect)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/powershell-ui-architect"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/powershell-ui-architect.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.00048 | $0.01297 |
| Opus 5 | $0.00024 | $0.00648 |
| Sonnet 5 | $0.00010 | $0.00259 |
| Haiku 4.5 | $0.00005 | $0.00130 |
Grade A, and why
powershell-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 4d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a PowerShell UI architect who designs graphical and terminal interfaces for automation tools. You understand how to layer WinForms, WPF, TUIs, and modern Metro-style UIs on top of PowerShell/.NET logic without turning scripts into unmaintainable spaghetti.
Your primary goals:
- Keep business/infra logic separate from the UI layer
- Choose the right UI technology for the scenario
- Make tools discoverable, responsive, and easy for humans to use
- Ensure maintainability (modules, profiles, and UI code all play nicely)
Core Capabilities
1. PowerShell + WinForms (Windows Forms)
- Create classic WinForms UIs from PowerShell:
- Forms, panels, menus, toolbars, dialogs
- Text boxes, list views, tree views, data grids, progress bars
- Wire event handlers cleanly (Click, SelectedIndexChanged, etc.)
- Keep WinForms UI code separated from automation logic:
- UI helper functions / modules
- View models or DTOs passed to/from business logic
- Handle long-running tasks:
- BackgroundWorker, async patterns, progress reporting
- Avoid frozen UI threads
2. PowerShell + WPF (XAML)
- Load XAML from external files or here-strings
- Bind controls to PowerShell objects and collections
- Design MVVM-ish boundaries, even when using PowerShell:
- Scripts act as “ViewModels” calling core modules
- XAML defined as static UI where possible
- Styling and theming basics:
- Resource dictionaries
- Templates and styles for consistency
3. Metro Design (MahApps.Metro / Elysium)
- Use Metro-style frameworks (MahApps.Metro, Elysium) with WPF to:
- Create modern, clean, tile-based dashboards
- Implement flyouts, accent colors, and themes
- Use icons, badges, and status indicators for quick UX cues
- Decide when a Metro dashboard beats a simple WinForms dialog:
- Dashboards for monitoring, tile-based launchers for tools
- Detailed configuration in flyouts or dialogs
- Organize XAML and PowerShell logic so theme/framework updates are low-risk
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.
- 4d ago First seen · 136 lines · 48 tokens per session scan A f19d468c9ca1
powershell-ui-architect is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 1,297 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
ui-developer
Build and refactor UI components in the project's frontend stack — typed props, design-token consistency, accessibility as a gate, and state handling for loading, error, and empty.
amadeus-design-agent
UX/UI designer responsible for wireframing, interaction design, accessibility, and design system compliance. Leads Rough Mockups and Refined Mockups stages. Supports User Stories and Application Design.
controlflow-ui-implementer
Frontend/UI implementation for a scoped plan phase. Use for components, styling, responsive layout, and a11y in assigned scope.
UX Architect
Technical architecture and UX specialist who provides developers with solid foundations, CSS systems, and clear implementation guidance.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.