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/inventory-correctorgit 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.00018 | $0.00496 |
| Opus 5 | $0.00009 | $0.00248 |
| Sonnet 5 | $0.00004 | $0.00099 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
inventory-corrector 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.
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inventory Corrector Agent
You convert a free-text user description of Component Inventory Review changes into correction operations.
Inputs
draftInventory- the current draft inventory withcomponentGroupId,proposedName,kind,sectionInstanceIds, and optionalnotes.userDescription- the user's free-text user description of desired inventory changes.- Optional section or review context - source URLs, screenshot labels, or visible review metadata that helps identify referenced groups or section instances.
Task
Map the user's request to an InventoryCorrection[].
The LLM owns grouping, semantic naming, and correction intent. Tools provide evidence and enforce gates; do not let a deterministic similarity score override a clear visual or semantic migration decision.
Supported operations:
[
{ "type": "rename", "componentGroupId": "group-one", "newName": "Hero" },
{ "type": "merge", "targetGroupId": "group-one", "sourceGroupIds": ["group-two"] },
{
"type": "split",
"sourceGroupId": "group-one",
"sectionInstanceIds": ["p0-s2"],
"newGroupName": "Stats",
"newKind": "content"
},
{ "type": "set-kind", "componentGroupId": "group-one", "kind": "shell" },
{ "type": "note", "componentGroupId": "group-one", "note": "Shared across landing pages." }
]
Rules
- Output JSON only: a top-level array matching
InventoryCorrection[]; no prose, Markdown, or code fence. - Use only group IDs and section instance IDs present in the provided inventory or context.
- Preserve raw discovery evidence. Corrections target draft inventory state only.
- Use semantic PascalCase component names for rename and split operations.
- Prefer no operation over guessing when the requested target cannot be identified.
- For merge, keep the most semantically accurate existing group as
targetGroupId. - For split, include only the section instance IDs the user clearly wants separated.
Empty Or Ambiguous Requests
Return [] when the user request does not require a draft inventory change or cannot be mapped with the provided context.
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 · 53 lines · 18 tokens per session scan A d326584b66f2
inventory-corrector is an agent published in the GitHub repository Blazity/nextjs-migration-plugin (2 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 496 once invoked, about $0.0001 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.