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 skills add sarveshtalele/mcp-skills-registry --skill ui-modernizationgit clone --depth 1 https://github.com/sarveshtalele/mcp-skills-registryWrote 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/sarveshtalele/mcp-skills-registry/ui-modernization)<a href="https://agentmods.dev/skills/sarveshtalele/mcp-skills-registry/ui-modernization"><img src="https://agentmods.dev/badge/skills/sarveshtalele/mcp-skills-registry/ui-modernization/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/skills/sarveshtalele/mcp-skills-registry/ui-modernization"><img src="https://agentmods.dev/badge/skills/sarveshtalele/mcp-skills-registry/ui-modernization.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.00053 | $0.00513 |
| Opus 5 | $0.00026 | $0.00257 |
| Sonnet 5 | $0.00011 | $0.00103 |
| Haiku 4.5 | $0.00005 | $0.00051 |
Grade A, and why
ui-modernization 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 12d 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.
What it actually says
ui-modernization
Plan a legacy UI migration to a modern component framework (React by default): component inventory, target tree, and starter stubs.
When to use
When modernizing a front end. Triggers: modernize UI, convert to React, UI migration, frontend modernization.
Inputs
screens(array of strings, required) — legacy screen/page names.framework(string, optional, defaultreact).
Outputs
plan_markdown— inventory, target tree, approach, definition of done.components— derived component names.sample_component— a starter component stub.
How it works
Derives PascalCase component names from screen names, builds a target tree, and emits a strangler migration approach with a per-screen DoD.
User stories
- As a front-end lead, I get a component map and a sample to start porting.
Edge cases
- A single screen passed as a string is accepted.
- Empty screen list → clear error (nothing to plan).
- Messy names with punctuation → sanitised into valid component identifiers.
Files
See DOCS.md. Figma mapping guidance lives in figma/.
What ships with it
7 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.
- 12d ago First seen · 72 lines · 53 tokens per session scan A b18fc78de03a
ui-modernization is a skill published in the GitHub repository sarveshtalele/mcp-skills-registry (2 stars, last pushed 11d ago), licensed MIT. It adds 53 tokens to every session and 513 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 skills, from other repositories
react-testing
React component testing with React Testing Library, Vitest/Jest, MSW for network mocking, accessibility assertions with axe, and the decision boundary between component tests and Playwright/Cypress end-to-end runs. Use when writing or fixing tests for React components, hooks, or pages.
react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
compiler-commit
Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.
compiler-port
Port a compiler pass from TypeScript to Rust. Gathers context, plans the port, implements in a subagent with test-fix loop, then reviews.
compiler-verify
Use when you need to run all compiler checks (tests, lint, format) before committing. Detects whether TS or Rust code changed and runs the appropriate checks.
frontend-feature
Build a new page, view, or data-driven feature in the Next.js frontend. Use when adding a route under the dashboard/marketing area, wiring UI to a backend endpoint, adding client state, or creating a localized page. Covers App Router, data fetching, Zustand stores, and i18n.