Borrowing it
Nothing to install: this file belongs to saeed-vayghan/gemini-agent-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/saeed-vayghan/gemini-agent-skills/master/.gemini/skills/powershell-ui-architect/SKILL.mdgit clone --depth 1 https://github.com/saeed-vayghan/gemini-agent-skillsWrote 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/skills/saeed-vayghan/gemini-agent-skills/powershell-ui-architect)<a href="https://agentmods.dev/skills/saeed-vayghan/gemini-agent-skills/powershell-ui-architect"><img src="https://agentmods.dev/badge/skills/saeed-vayghan/gemini-agent-skills/powershell-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/skills/saeed-vayghan/gemini-agent-skills/powershell-ui-architect"><img src="https://agentmods.dev/badge/skills/saeed-vayghan/gemini-agent-skills/powershell-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.00064 | $0.01303 |
| Opus 5.5 | $0.00026 | $0.00521 |
| Sonnet 5.5 | $0.00013 | $0.00261 |
| Haiku 4.5 | $0.00006 | $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 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 — 138 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.
- 1mo ago First seen · 138 lines · 64 tokens per session scan A 3429c7c30d82
powershell-ui-architect is a skill published in the GitHub repository saeed-vayghan/gemini-agent-skills (48 stars, last pushed 9mo ago), licensed MIT. It adds 64 tokens to every session and 1,303 once invoked, about $0.0003 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 skills, from other repositories
frontend-ui-engineering
Front-load UI construction decisions — component boundary and prop API, state placement, required states, responsiveness, accessibility. Use when creating or refactoring a component, page, or design-system primitive. Don't use for pure logic (/tdd), throwaway exploration (/prototype), or auditing finished UI…
frontend-ui-engineering
Build accessible, responsive UI components avoiding generic AI aesthetic. Bootstrap on demand.
rayden-code
Generate React code with Rayden UI components using correct props, tokens, and premium layout patterns.
tailwind-design-system
Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.
web-design-review
Review built UI: hierarchy, consistency, polish, responsive layout, dashboards, design-system drift, prototypes.
accessibility-audit
Audit accessibility to WCAG 2.2: semantic HTML, keyboard, focus, contrast, labels, screen readers.