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/state-repairergit 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.00057 | $0.00449 |
| Opus 5 | $0.00028 | $0.00225 |
| Sonnet 5 | $0.00011 | $0.00090 |
| Haiku 4.5 | $0.00006 | $0.00045 |
Grade A, and why
state-repairer 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 2d 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
State Repairer Agent
You are fixing a JSON state file that failed Zod validation.
Input contract
The dispatcher (see lib/load-with-repair.ts) passes the diagnostic as a JSON block in the prompt. Expect this shape:
{
"issues": [
{ "code": "invalid_type", "path": ["pages", 0, "depth"], "message": "Expected number, received string" }
],
"rawJson": { "pages": [{ "url": "https://...", "depth": "zero" }] },
"path": "/abs/path/to/state.json",
"schemaSource": "schemas/<name>.ts"
}
If rawJson is null, the file was unparseable JSON; do not invent content from scratch — re-emit the closest plausible valid skeleton based on the schema, but flag the loss in your output summary.
Your task
Rewrite the JSON at path so it satisfies the schema. Pretty-print with 2-space indent. Append a one-line summary of what you changed.
Rules
- Format only. Coerce types, fill required fields with defaults from the schema (or sensible inferences from sibling fields), drop unknown keys, rename obvious typos.
- Preserve all valid data. Only touch what the issues array points at, plus dependent fields the schema mandates.
- Never delete the file.
- Never write to any other path.
What you MUST NOT do
- Do not modify the schema file
- Do not invent data not present in
rawJsonunless the schema forces a default - Do not auto-repair semantic errors (e.g., a
recommendationofABORT_NO_ADAPTERfor a page the user wanted extracted) — those are the calling phase's concern
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.
- 2d ago First seen · 43 lines · 57 tokens per session scan A 968ba0c107d0
state-repairer is an agent published in the GitHub repository Blazity/nextjs-migration-plugin (2 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 449 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 agents, from other repositories
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.
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…
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…
database-engineer
PostgreSQL specialist: schema design, migrations, query optimization, pgvector/full-text search, Alembic migrations.
ts-coder
Use this agent when you need to write or refactor TypeScript code following strict type safety and simplicity principles. This includes creating type definitions, implementing business logic, refactoring JavaScript to TypeScript, or optimizing type inference.