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/feigecode/navop/gpui-componentnpx skills add feigeCode/navop --skill gpui-componentgit clone --depth 1 https://github.com/feigeCode/navopWrote 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/feigecode/navop/gpui-component)<a href="https://agentmods.dev/skills/feigecode/navop/gpui-component"><img src="https://agentmods.dev/badge/skills/feigecode/navop/gpui-component.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.00112 | $0.02230 |
| Opus 5 | $0.00056 | $0.01115 |
| Sonnet 5 | $0.00022 | $0.00446 |
| Haiku 4.5 | $0.00011 | $0.00223 |
Grade A, and why
gpui-component 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 5d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 169 lines · 112 tokens per session scan A 2902632900ca
gpui-component is a skill published in the GitHub repository feigeCode/navop (832 stars, last pushed 5d ago), with no licence file. It adds 112 tokens to every session and 2,230 once invoked, about $0.0006 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-30.
Other skills, from other repositories
cranpose
Cranpose UI framework conventions, APIs, and patterns. Use when writing Cranpose composables, state, layout, or modifiers, or when working in a project that depends on the cranpose crates.
ratatui-charm-polish
Build beautiful Rust TUIs with ratatui that match the polish of Charmbracelet apps (slides, gum, lazygit, yazi). Use when building or restyling a Rust terminal UI, choosing TUI crates, designing a theme, or making a ratatui app look expensive.
product-design
The rulebook for keeping new features visually + behaviourally consistent. When in doubt, COPY the closest existing component rather than inventing. Full token values and file paths: docs/knowledge/product-design.md.
ui-ux-audit
Automated UI/UX + accessibility audit for the ClickHouse Monitor dashboard (apps/dashboard-tsr). Use this whenever the user wants to "test all pages", "audit the dashboard", "find UI/UX issues", "check accessibility / a11y", "spot visual regressions", "screenshot every route", "reproduce a UI bug", or asks to verify…
ratatui-tui
Build terminal UIs with ratatui following 2026 Rust best practices. Use when: (1) Creating new TUI apps, (2) Adding widgets/layouts, (3) Keyboard navigation/state management, (4) Image integration via ratatui-image, (5) Async event handling, (6) Release optimization. Covers v0.30.0+ API, Elm Architecture…
project-chmonitor-verify-skill
Project-local .cursor/skills/verify-chmonitor drives the Rust CLI; default doctor is identity-only.