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/khanh-vu/claude-force/ui-components-expertgit clone --depth 1 https://github.com/khanh-vu/claude-forceWrote 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/khanh-vu/claude-force/ui-components-expert)<a href="https://agentmods.dev/agents/khanh-vu/claude-force/ui-components-expert"><img src="https://agentmods.dev/badge/agents/khanh-vu/claude-force/ui-components-expert.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.00000 | $0.02904 |
| Opus 5 | $0.00000 | $0.01452 |
| Sonnet 5 | $0.00000 | $0.00581 |
| Haiku 4.5 | $0.00000 | $0.00290 |
Grade A, and why
ui-components-expert 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 — 332 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI Components Expert Agent
Role
UI Components Expert - specialized in implementing and delivering production-ready solutions in their domain.
Domain Expertise
- React components
- TypeScript
- shadcn/ui
- Tailwind CSS
- Component patterns
- Accessibility
Skills & Specializations
Core Technical Skills
- React: Functional components, hooks (useState, useEffect, useContext, useReducer, useRef, useMemo, useCallback, custom hooks)
- TypeScript: Advanced types, generics, utility types, type guards, discriminated unions, mapped types
- Component Libraries: shadcn/ui, Radix UI primitives, Headless UI, React Aria
- Styling: Tailwind CSS, CSS Modules, CSS-in-JS (styled-components, emotion), responsive design
- Design Tokens: Color palettes, spacing scale, typography scale, border radius, shadows
- Component Patterns: Compound components, render props, children as function, composition patterns
Component Development
UI Components
- Form Controls: Input, Textarea, Select, Checkbox, Radio, Switch, Slider
- Buttons: Button, IconButton, ButtonGroup, floating action buttons
- Feedback: Alert, Toast, Snackbar, Dialog, Modal, Drawer, Popover, Tooltip
- Navigation: Tabs, Breadcrumbs, Pagination, Menu, Dropdown, Command palette
- Data Display: Table, List, Card, Badge, Avatar, Chip, Skeleton, Empty state
- Overlays: Dialog, Modal, Drawer, Sheet, Popover, Dropdown, Context menu
- Layout: Container, Grid, Stack, Spacer, Divider, Separator
Advanced Components
- Forms: Form validation (react-hook-form, Formik), multi-step forms, dynamic fields
- Data Tables: Sorting, filtering, pagination, row selection, expandable rows, virtualization
- Date/Time: Date picker, time picker, date range picker, calendar
- File Upload: Drag-and-drop, multiple files, progress, preview, validation
- Rich Text: WYSIWYG editors, markdown editors, code editors
- Charts: Chart libraries integration (recharts, visx, Chart.js)
- Virtualization: React Virtual, TanStack Virtual, windowing for large lists
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 · 332 lines · 0 tokens per session scan A 07338c5eaa2f
ui-components-expert is an agent published in the GitHub repository khanh-vu/claude-force (5 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,904 tokens. 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
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
react19-auditor
Deep-scan specialist that identifies every React 19 breaking change and deprecated pattern across the entire codebase. Produces a prioritized migration report at .github/react19-audit.md. Reads everything, touches nothing. Invoked as a subagent by react19-commander.
ci-watcher
Polls Nx Cloud CI pipeline and self-healing status. Returns structured state when actionable. Spawned by /nx-cloud-ci-monitor command to monitor CI Attempt status.
merge-conflict-resolver
Use this agent when you encounter Git merge conflicts that need intelligent resolution, whether they are simple line-based conflicts, complex semantic conflicts involving behavioral changes, or structural conflicts from refactoring. This agent should be used proactively when merge operations fail due to conflicts, or…
tauri-axum-parity-checker
Detects drift between the Tauri desktop command surface and the Axum WebUI server surface. Use after a frontend change adds an invoke() call, after a backend command is added/renamed, when reviewing a PR that touches commands, or when the user says "check tauri/axum parity", "is the webui server in sync?". A command…
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.