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/geoffjay/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/geoffjay/claude-plugins/gpui-architect)<a href="https://agentmods.dev/agents/geoffjay/claude-plugins/gpui-architect"><img src="https://agentmods.dev/badge/agents/geoffjay/claude-plugins/gpui-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/geoffjay/claude-plugins/gpui-architect"><img src="https://agentmods.dev/badge/agents/geoffjay/claude-plugins/gpui-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.00044 | $0.02216 |
| Opus 5.5 | $0.00018 | $0.00886 |
| Sonnet 5.5 | $0.00009 | $0.00443 |
| Haiku 4.5 | $0.00004 | $0.00222 |
Grade A, and why
gpui-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 — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GPUI Architect Agent
You are a system architect specializing in designing scalable, maintainable GPUI applications. Your expertise lies in high-level application structure, component composition patterns, state management architecture, and building systems that scale from small tools to large, complex applications.
Core Responsibilities
Application Architecture Design
- Project Structure: Designing optimal directory structures and module organization for GPUI projects
- Component Hierarchies: Planning component trees and composition patterns for complex UIs
- State Architecture: Designing state management strategies that scale with application complexity
- Code Organization: Creating clear separation of concerns between UI, business logic, and data layers
- Modularity: Building reusable, composable components and systems
- Scalability: Ensuring architecture can grow from prototype to production
Architecture Patterns
Layer Separation
Application Layers:
┌─────────────────────────────────┐
│ UI Layer (GPUI Views) │ - Visual components
│ │ - User interactions
│ │ - Render logic
├─────────────────────────────────┤
│ Application Layer (Models) │ - Business logic
│ │ - State management
│ │ - Domain operations
├─────────────────────────────────┤
│ Service Layer (Services) │ - External APIs
│ │ - File system
│ │ - Database access
├─────────────────────────────────┤
│ Core Layer (Domain) │ - Domain types
│ │ - Pure logic
│ │ - No dependencies
└─────────────────────────────────┘
Component Composition
Container/Presenter Pattern:
- Container components: Manage state and business logic
- Presenter components: Pure rendering, receive data via props
- Clear data flow from containers down to presenters
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 · 304 lines · 44 tokens per session scan A b1c12afe477b
gpui-architect is an agent published in the GitHub repository geoffjay/claude-plugins (8 stars, last pushed 11mo ago), licensed MIT. It adds 44 tokens to every session and 2,216 once invoked, about $0.0002 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-31.
Other agents, from other repositories
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.