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.
git clone --depth 1 https://github.com/Matt-Dionis/claude-code-configsWrote 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/commands/matt-dionis/claude-code-configs/migrate-to-app-router)<a href="https://agentmods.dev/commands/matt-dionis/claude-code-configs/migrate-to-app-router"><img src="https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/migrate-to-app-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/commands/matt-dionis/claude-code-configs/migrate-to-app-router"><img src="https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/migrate-to-app-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.00008 | $0.00372 |
| Opus 5 | $0.00004 | $0.00186 |
| Sonnet 5 | $0.00002 | $0.00074 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade A, and why
migrate-to-app-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 10d 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
Migrate Pages Router to App Router for: $ARGUMENTS
Migration Steps
-
Analyze Current Structure
- Identify pages to migrate
- Check for getServerSideProps, getStaticProps, getStaticPaths
- Find _app.tsx and_document.tsx customizations
-
Create App Router Structure
- Create corresponding app/ directory structure
- Convert pages to page.tsx files
- Extract layouts from _app.tsx
-
Migrate Data Fetching
- getStaticProps → Direct fetch in Server Component
- getServerSideProps → Direct fetch in Server Component
- getStaticPaths → generateStaticParams
- API calls in useEffect → Keep in Client Component or move to Server
-
Update Routing Hooks
- useRouter from next/router → next/navigation
- Update router.push() calls
- Handle query params with useSearchParams
-
Migrate Metadata
- Head component → metadata export or generateMetadata
- Update SEO configuration
-
Handle Special Files
- _app.tsx → app/layout.tsx
- _document.tsx → app/layout.tsx (html/body tags)
- _error.tsx → app/error.tsx
- 404.tsx → app/not-found.tsx
-
Test and Validate
- Ensure all routes work
- Verify data fetching
- Check that layouts render correctly
- Test client-side navigation
Create a migration log documenting all changes and any issues that need manual review.
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.
- 10d ago First seen · 49 lines · 8 tokens per session scan A 09fe4281e6ce
migrate-to-app-router is a command published in the GitHub repository Matt-Dionis/claude-code-configs (624 stars, last pushed 1y ago), licensed MIT. It adds 8 tokens to every session and 372 once invoked, about $0.0000 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 commands, from other repositories
prototype-loop
Enter leveraged-prototype focus mode — focus marker plus normal watch/rebuild loop for visual-parity work and batch upstream framework gap-fixes.
review-arch
Review the current branch for code quality, TypeScript, and React/Next.js patterns. Supports whole-branch review or scoped review by path, feature, or base branch.
a11y-audit-react
Identify accessibility violations in React components and provide actionable remediation aligned with WCAG 2.2 Level AA. This is the guided audit workflow that applies the standards defined in the a11y-automation and react-components rules.
react-build
Fix React build failures (Vite, webpack, Next.js, CRA, Parcel, esbuild, Bun) incrementally — JSX/TSX compile errors, hydration mismatches, server/client component boundary failures, missing types. Invokes the react-build-resolver agent for minimal, surgical fixes.
next-upgrade
Structured workflow for upgrading Next.js applications across major versions. Use when migrating a Next.js project from one major version to another (e.g., 13 to 14, 14 to 15, 15 to 16). Covers codemod automation, breaking change detection, incremental migration paths, and post-upgrade validation.
web-design
Design and build a complete website or webapp from a project brief — end-to-end workflow from design to working React/Vite code.