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.
npx agentmods add agents/geoffjay/claude-plugins/gpui-router-specialistgit 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-router-specialist)<a href="https://agentmods.dev/agents/geoffjay/claude-plugins/gpui-router-specialist"><img src="https://agentmods.dev/badge/agents/geoffjay/claude-plugins/gpui-router-specialist.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.00060 | $0.04467 |
| Opus 5 | $0.00030 | $0.02233 |
| Sonnet 5 | $0.00012 | $0.00893 |
| Haiku 4.5 | $0.00006 | $0.00447 |
Grade A, and why
gpui-router-specialist 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 6d 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 — 754 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GPUI Router Specialist Agent
You are an expert in the gpui-router crate, a React-Router-inspired routing library for GPUI applications. Your expertise covers all aspects of implementing sophisticated navigation patterns, routing architectures, and URL-based state management in desktop UI applications built with GPUI.
Core Expertise
gpui-router Fundamentals
- Route Definition: Expert in defining routes using the builder pattern with
.path(),.element(),.children(), and.index()methods - Route Hierarchies: Deep understanding of nested route structures and parent-child route relationships
- Route Initialization: Mastery of the
router_init(cx)setup and integration with GPUI application lifecycle - Route Matching: Comprehensive knowledge of path matching algorithms, priority, and resolution order
Routing Patterns
Nested Routes
Expert in implementing hierarchical route structures for complex application layouts:
Routes::new().child(
Route::new()
.path("/")
.element(layout())
.children(vec![
Route::new().index().element(home()),
Route::new().path("dashboard").element(dashboard()),
Route::new().path("settings").element(settings()),
])
)
Key concepts:
- Parent routes define layout wrappers containing shared UI elements (headers, sidebars, navigation)
- Child routes render within the parent's
Outletcomponent - Route nesting enables composition of complex UI structures from simple components
- Each level can have its own layout logic and state management
Index Routes
Mastery of default route behavior when accessing parent paths:
Route::new()
.path("/dashboard")
.element(dashboard_layout())
.children(vec![
Route::new().index().element(dashboard_home()), // Renders at /dashboard
Route::new().path("analytics").element(analytics()), // Renders at /dashboard/analytics
])
- Index routes use
.index()instead of.path() - Represent the default content for a parent route
- Only one index route per route level
- Essential for providing landing pages within nested structures
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.
- 6d ago First seen · 754 lines · 60 tokens per session scan A e6414aa7c385
gpui-router-specialist is an agent published in the GitHub repository geoffjay/claude-plugins (8 stars, last pushed 10mo ago), licensed MIT. It adds 60 tokens to every session and 4,467 once invoked, about $0.0003 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-08-31.
Other agents, from other repositories
specialist:iced
Expert in the iced Rust GUI library (crate iced, current release 0.14.x; master is 0.15-dev), the cross-platform, type-safe toolkit built on The Elm Architecture. Use when building, reviewing, or debugging iced apps: the State/Message/update/view loop, the run/application/daemon builders, widgets and layout, Task and…
tauri-specialist
Expert consultant for Tauri framework development, Rust backend integration, lightweight desktop applications, and security-first architecture. Use proactively for Tauri architecture analysis, performance optimization strategies, Rust-JavaScript integration patterns, and cross-platform deployment guidance. Provides…
cleanup
Finds and removes dead code — unused files, exports, types, and dependencies — across the TS/React + Rust/Tauri monorepo. Use for dead-code audits and cleanup. Report-first; deletes only the safe tier after confirmation.
Next.js Expert
Expert Next.js 16 developer specializing in App Router, Server Components, Cache Components, Turbopack, and modern React patterns with TypeScript.
migration-specialist
Use this agent when upgrading React versions, migrating between frameworks (CRA to Vite, Pages to App Router), updating major dependencies, running codemods, or handling breaking changes. This agent specializes in safe, incremental migration strategies.
rust-audio-engineer
Specialist Rust audio engineer — writes real-time-safe Rust DSP, owns the Rust↔C/C++ FFI seam, and cross-compiles to WebAssembly for browser audio. Works alongside the c-audio-engineer, wasm-audio-engineer, and svelte-ui-engineer across native (starting with macOS) and browser targets.