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 woliveiras/geremmyas --skill migrate-react-routergit clone --depth 1 https://github.com/woliveiras/geremmyasWrote 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/woliveiras/geremmyas/migrate-react-router)<a href="https://agentmods.dev/skills/woliveiras/geremmyas/migrate-react-router"><img src="https://agentmods.dev/badge/skills/woliveiras/geremmyas/migrate-react-router/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/woliveiras/geremmyas/migrate-react-router"><img src="https://agentmods.dev/badge/skills/woliveiras/geremmyas/migrate-react-router.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.00048 | $0.00783 |
| Opus 5 | $0.00024 | $0.00392 |
| Sonnet 5 | $0.00010 | $0.00157 |
| Haiku 4.5 | $0.00005 | $0.00078 |
Grade A, and why
migrate-react-router 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 9d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate React Router v6 to v7
Step-by-step guide for migrating a React Router v6 codebase to v7 framework mode.
When to Use
- Upgrading an existing app from React Router v6 to v7
- Converting classic
<BrowserRouter>setup to framework mode - Systematic migration of route files
Breaking Changes Reference
Imports: react-router replaces react-router-dom
// ❌ v6
import { Link, useNavigate, Form } from "react-router-dom"
// ✅ v7
import { Link, useNavigate, Form } from "react-router"
Removed APIs
| v6 | v7 Replacement |
|---|---|
json() helper |
Return plain objects from loaders |
defer() |
Use native promises and <Awaited> |
<BrowserRouter> (classic mode) |
Framework mode with file-based routes |
useLoaderData() hook |
loaderData prop on component |
File-Based Routing
Routes are defined by file structure in app/routes/:
app/routes/
├── _index.tsx → /
├── books.tsx → /books (layout)
├── books._index.tsx → /books (index)
├── books.$id.tsx → /books/:id
└── books.$id.edit.tsx → /books/:id/edit
.separates URL segments:books.$id→/books/:id_prefix = pathless layout:_auth.tsxwraps without adding URL segment$prefix = dynamic param:$id→:id
Loader Data Access
// ❌ v6
export default function BookPage() {
const data = useLoaderData()
return <h1>{data.book.title}</h1>
}
// ✅ v7
export default function BookPage({ loaderData }: Route.ComponentProps) {
const { book } = loaderData
return <h1>{book.title}</h1>
}
Typegen
v7 generates route types automatically. Use Route.* types:
import type { Route } from "./+types/book"
export async function loader({ params }: Route.LoaderArgs) { ... }
export default function BookPage({ loaderData }: Route.ComponentProps) { ... }
Migration Procedure
- Update dependencies:
npm install react-router@latest(removereact-router-dom) - Fix imports: search and replace
react-router-dom→react-routeracross all files - Remove
json()calls: return plain objects from loaders/actions - Remove
defer()calls: use native promises - Convert route definitions: move from
<Route>components to file-based routes inapp/routes/ - Update components: replace
useLoaderData()withloaderDataprop - Add typegen: use
Route.*types from generated+typesfiles - Run tests: verify all routes load correctly
- Remove old router setup: delete
<BrowserRouter>/createBrowserRouterconfiguration
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.
- 9d ago First seen · 99 lines · 48 tokens per session scan A bb06550606d8
migrate-react-router is a skill published in the GitHub repository woliveiras/geremmyas (10 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 783 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
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.
dashboard-widgets
Author a dashboard widget — a small React component backed by named LangWatchQL queries — from a plain question. Discovers the analytics schema, writes the queries, writes the widget file, saves it, then proves it renders. Use when asked to build, prototype, or iterate on a custom chart widget, or to add a widget…
assistant-ui-primitives
Guide for assistant-ui UI primitives - ThreadPrimitive, ComposerPrimitive, MessagePrimitive. Use when customizing chat UI components.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…