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/blazity/nextjs-migration-plugin/route-mappergit clone --depth 1 https://github.com/Blazity/nextjs-migration-pluginWhat 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.00046 | $0.00504 |
| Opus 5 | $0.00023 | $0.00252 |
| Sonnet 5 | $0.00009 | $0.00101 |
| Haiku 4.5 | $0.00005 | $0.00050 |
Grade A, and why
route-mapper 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 yesterday.
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
Route Mapper Agent
You take the algorithmic route output from lib/route-map.ts and refine it.
Inputs
routes—{ sourceUrl, nextRoute, params, kind }[]produced bylib/route-map.tscrawl— original crawl metadata (page titles, depths)
Rules
- Trust the algorithm by default.
lib/route-map.tscollapses sibling URL groups of size ≥ 3 into[slug]patterns. Do not lower the threshold. - Override only when the algorithm is clearly wrong:
- The same parent has both an index page and 3+ sibling children → mark the index as
kind: "static"and the children askind: "dynamic"(the algorithm already does this; verify). - Sibling URLs that share a common token but represent unrelated pages should NOT be promoted. If you spot such a false-positive group, demote them all back to
staticand explain innotes.
- The same parent has both an index page and 3+ sibling children → mark the index as
- Catch-all routes are out of scope for v1. Emit only
staticanddynamickinds. - Locale prefixes (e.g.,
/en,/fr) — leave alone for v1; treat as ordinary path segments.
Output
A Routes object matching schemas/routes.ts:
{
"routes": [
{ "sourceUrl": "...", "nextRoute": "/", "params": {}, "kind": "static" },
{ "sourceUrl": "...", "nextRoute": "/case-study/[slug]", "params": { "slug": "cookunity" }, "kind": "dynamic" }
],
"updatedAt": "<ISO>"
}
Plus an optional notes: string[] array surfacing any overrides you applied.
You MUST NOT
- Invent routes for URLs that aren't in the input.
- Modify
components.json,layouts.json, orprops.json. - Introduce route patterns that don't exist in Next.js App Router (
[slug],[...slug],(group)are valid; v1 emits only[slug]).
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.
- yesterday First seen · 45 lines · 46 tokens per session scan A 36f85a4a1272
route-mapper is an agent published in the GitHub repository Blazity/nextjs-migration-plugin (2 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 504 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 agents, from other repositories
rot-sweeper
Use after a change to remove what it deprecated — now-unused npm dependencies, orphaned files/components/styles, dead exports, stale config/scripts. Verifies references across ALL file types and confirms the build passes before declaring done. Surfaces untracked/unrecoverable or load-bearing deletions for human…
claudemd-maintainer
Use right after any substantive repo change to keep CLAUDE.md accurate. Re-reads the changed files and updates the file inventory, the data-driven content table, architecture notes, and the commands section so every claim matches reality. Read-only except for CLAUDE.md.
docs-syncer
Use after a change to sync the human-facing docs — README.md, data/ADDINGCONTENT.md, and affected code comments/inline docstrings — with the new reality. Leaves CLAUDE.md to claudemd-maintainer.
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…
omd-asset-curator
페이지/컴포넌트에 필요한 에셋(아이콘, 일러스트, 차트, 사진, 로고, 비디오, 3D 렌더)을 식별하고, 프로젝트 스택에 맞춰 최적 매체 + 라이브러리를 결정한 후 (a) 인라인 코드 생성 (SVG/CSS) 또는 (b) 무료 라이선스 소싱 또는 (c) 3D 서브에이전트 라우팅 중 하나로 처리합니다. 이모지 디폴트 금지 — SVG 우선.
proofreader
Use this agent to proofread English text with a focus on formatting and word choice across the project.