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/inventory-corrector)<a href="https://agentmods.dev/agents/blazity/nextjs-migration-plugin/inventory-corrector"><img src="https://agentmods.dev/badge/agents/blazity/nextjs-migration-plugin/inventory-corrector/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/inventory-corrector"><img src="https://agentmods.dev/badge/agents/blazity/nextjs-migration-plugin/inventory-corrector.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.00018 | $0.00496 |
| Opus 5.5 | $0.00007 | $0.00198 |
| Sonnet 5.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 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 — 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.
- 1mo ago 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 25d ago), licensed MIT. It adds 18 tokens to every session and 496 once invoked, about $0.0001 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
solution-diagrammer
Draws one evidence-grounded architecture diagram as an editable draw.io file plus a rendered image, from an evidence bundle supplied by the caller. Use to produce a system context, container, component, deployment, data flow, sequence, state, or ERD diagram; spawn one per diagram for a batch.
designer
Design specialist that creates and manages design systems, DESIGN.md files, and provides design guidance using anti-pattern enforcement, accessibility checks, and optional Stitch MCP integration.
stitch-kit
Use this agent for anything Stitch-related: ideating designs through conversation, generating UI screens from text, editing/iterating designs, generating design variants, managing Stitch Design Systems, converting designs to production code, extracting design tokens, and running the full design-to-ship pipeline.…
fe-a11y-auditor
Specialized accessibility (a11y) audit — semantic HTML, ARIA, keyboard navigation, color contrast, focus management. More precise than fe-reviewer's a11y axis. READ-ONLY. With --live, also measures via Chrome DevTools MCP (Lighthouse a11y score, real accessibility tree, runtime console); falls back to static analysis…
fe-vision
Precisely extracts layout, components, color, and typography from a single screen in Figma, screenshots, UI mockups, design drafts, or PDF/PPT (via conversion) — extraction mode. Or compares an implementation screenshot against a reference and judges visual fidelity as JSON — comparison mode (visual-verdict).…
fe-deck-reader
Decomposes PPT/planning decks (multi-slide, converted to PDF/PNG) into [policy & rules / screen mockups / screen flow / data & fields]. Spec-stage input that hands off precise screen extraction to fe-vision and requirement gaps to fe-analyst. READ-ONLY.