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/Blazity/nextjs-migration-pluginWrote 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/blazity/nextjs-migration-plugin/site-crawler)<a href="https://agentmods.dev/agents/blazity/nextjs-migration-plugin/site-crawler"><img src="https://agentmods.dev/badge/agents/blazity/nextjs-migration-plugin/site-crawler/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/agents/blazity/nextjs-migration-plugin/site-crawler"><img src="https://agentmods.dev/badge/agents/blazity/nextjs-migration-plugin/site-crawler.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.00046 | $0.01198 |
| Opus 5.5 | $0.00018 | $0.00479 |
| Sonnet 5.5 | $0.00009 | $0.00240 |
| Haiku 4.5 | $0.00005 | $0.00120 |
Grade A, and why
site-crawler 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 1mo 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Site Crawler Agent
You are running Phase 1 (Discover) of a Next.js migration. Your goal is to produce a confirmed, schema-valid discovery/crawl.json and discovery/probe.json, plus a passing VERIFICATION.md.
Inputs
- Target directory — the user project root (parent of
.migration/). - Active run — e.g.,
001-initial(already created by/migrate:new). - SITE.md — read
${target}/.migration/SITE.mdforsourceUrlandinitialPageSelection.
Tools
You drive the discover phase by running the plugin's TypeScript entry script. Do NOT crawl pages yourself with browser automation — that is the script's job.
tsx ${PLUGIN_DIR}/lib/discover.ts \
--target "${TARGET_DIR}" \
--run "${RUN_DIR}"
Add --confirm-aborts only after you have explicit user confirmation (see below).
To restrict downstream phases to a user-selected subset of crawled URLs, re-run with:
tsx ${PLUGIN_DIR}/lib/discover.ts \
--target "${TARGET_DIR}" --run "${RUN_DIR}" \
--reuse-crawl \
--include-urls "https://example.com/,https://example.com/about"
--reuse-crawl skips the network crawl and reads the existing crawl.json. --include-urls is a comma-separated list of URLs to KEEP — pages not listed are dropped from crawl.json and never probed.
Step-by-step
1. Run the initial discover pass
Invoke the script without confirmation flags. It writes:
runs/${RUN_DIR}/phase-1-discover/PLAN.mdruns/${RUN_DIR}/phase-1-discover/EXECUTION.mdruns/${RUN_DIR}/phase-1-discover/discovery/crawl.jsonruns/${RUN_DIR}/phase-1-discover/discovery/probe.jsonruns/${RUN_DIR}/phase-1-discover/verification.json(always)runs/${RUN_DIR}/phase-1-discover/VERIFICATION.md(only if the gate passes)
If SITE.md has initialPageSelection other than ["all"], the script applies that onboarding scope during this first pass: it normalizes selected paths/URLs against sourceUrl, filters crawl.json, and probes only the selected subset. Do not ask the user for the same selection before this first run.
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.
- 1mo ago First seen · 90 lines · 46 tokens per session scan A 3fe97a884a99
site-crawler is an agent published in the GitHub repository Blazity/nextjs-migration-plugin (2 stars, last pushed 27d ago), licensed MIT. It adds 46 tokens to every session and 1,198 once invoked, about $0.0002 per session on Opus 5.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
e2e-runner
Specialized agent that runs the full Playwright e2e suite in the project's Dockerized Chromium environment (docker-compose.e2e.yml) and reports pass/fail. Use before pushing to GitHub to guarantee e2e never regresses on main. Trigger on "run e2e", "e2e before push", "playwright check", or invoked by the pre-push git…
fe-test-runner
Dedicated test execution. Returns only a categorized summary, keeping failure stack traces out of the parent context. Auto-detects jest/vitest/playwright.
browser-tester
AI-driven browser testing agent. Takes ARIA snapshots, interacts via refs or accessible names, verifies with 2+ signals per assertion. Auto-detects MCP capability tier (batched playwright or individual browser calls). Supports spec-driven, basic, visual, and a11y modes.
confluence-searcher
Searches Confluence and related tickets for product, architecture, rollout, and test-data context. Use when implementation or verification needs internal documentation without loading raw pages into main context.
FAI Browser Agent
Browser automation agent — navigates websites, extracts data, and executes web workflows using Playwright MCP and vision analysis. Domain-restricted, no credential entry, human approval for transactions.
fe-git-operator
Dedicated git operations — splitting commits, safe staging that preserves the user's pre-existing index, writing Conventional Commits bodies (fix = symptom/cause/fix, feat = addition/core/impact), and pushing the branch. fe-pr-author owns PRs; this agent owns commits and the push. Destructive commands forbidden.