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 skills/geoffjay/claude-plugins/rust-ui-architecturenpx skills add geoffjay/claude-plugins --skill rust-ui-architecturegit 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/skills/geoffjay/claude-plugins/rust-ui-architecture)<a href="https://agentmods.dev/skills/geoffjay/claude-plugins/rust-ui-architecture"><img src="https://agentmods.dev/badge/skills/geoffjay/claude-plugins/rust-ui-architecture.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 | $0.00043 | $0.03554 |
| Opus 5 | $0.00022 | $0.01777 |
| Sonnet 5 | $0.00009 | $0.00711 |
| Haiku 4.5 | $0.00004 | $0.00355 |
Grade A, and why
rust-ui-architecture 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 — 607 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rust UI Architecture
Metadata
This skill provides comprehensive guidance on architecting scalable, maintainable Rust UI applications using GPUI, covering project structure, design patterns, and best practices.
Instructions
Application Structure
Recommended Project Layout
my-gpui-app/
├── Cargo.toml
├── src/
│ ├── main.rs # Application entry point
│ ├── app.rs # Main application struct
│ ├── ui/ # UI layer
│ │ ├── mod.rs
│ │ ├── views/ # High-level views
│ │ │ ├── mod.rs
│ │ │ ├── main_view.rs
│ │ │ ├── sidebar.rs
│ │ │ └── editor.rs
│ │ ├── components/ # Reusable components
│ │ │ ├── mod.rs
│ │ │ ├── button.rs
│ │ │ ├── input.rs
│ │ │ └── modal.rs
│ │ └── theme.rs # Theme definitions
│ ├── models/ # Application state
│ │ ├── mod.rs
│ │ ├── document.rs
│ │ ├── project.rs
│ │ └── settings.rs
│ ├── services/ # External integrations
│ │ ├── mod.rs
│ │ ├── file_service.rs
│ │ └── api_client.rs
│ ├── domain/ # Core business logic
│ │ ├── mod.rs
│ │ └── operations.rs
│ └── utils/ # Utilities
│ ├── mod.rs
│ └── helpers.rs
├── examples/ # Example applications
│ └── basic.rs
└── tests/ # Integration tests
├── integration/
└── ui/
Layer Separation
Four-Layer Architecture
┌─────────────────────────────────┐
│ UI Layer (Views) │ - GPUI views and components
│ │ - User interactions
│ │ - Render logic
├─────────────────────────────────┤
│ Application Layer (Models) │ - Application state (Model<T>)
│ │ - State coordination
│ │ - Business logic orchestration
├─────────────────────────────────┤
│ Service Layer (Services) │ - File I/O
│ │ - Network requests
│ │ - External APIs
├─────────────────────────────────┤
│ Domain Layer (Core) │ - Pure business logic
│ │ - Domain types
│ │ - No dependencies on UI/GPUI
└─────────────────────────────────┘
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 · 607 lines · 43 tokens per session scan A 7bc6bd44daef
rust-ui-architecture is a skill published in the GitHub repository geoffjay/claude-plugins (8 stars, last pushed 10mo ago), licensed MIT. It adds 43 tokens to every session and 3,554 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-08-31.
Other skills, from other repositories
lint-js
Lint JS/TS code only. Use before opening a PR when only JavaScript or TypeScript files were changed (no Rust).
rust-code-quality
Run a focused Rust quality review when the user requests one, when reviewing a Rust PR/commit, or when another selected review workflow delegates Rust-specific checks. Do not auto-load for every implementation edit.
rust-pro
Master modern Rust (2024 edition) with async patterns, advanced type system features, and production-ready systems programming. Expert in the current Rust ecosystem including Tokio, axum, and modern crates. Use PROACTIVELY for Rust development, performance optimization, or systems programming.
switchyard-rust-review
Review Switchyard Rust changes for correctness and maintainability. Use for pull requests or diffs touching crates, PyO3 bindings, async runtime behavior, streaming, protocol types, translation, algorithms, or LLM clients.
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
rust-system-calls
Guides using bunsys for system calls and file I/O in Rust. Use when implementing file operations, opening fds, or any syscall path instead of std::fs or libc.