inventory-corrector

inventory-corrector is an agent for Claude Code from Blazity/nextjs-migration-plugin. It costs 18 tokens per session (496 once invoked), scanned A, original, MIT.

An agent that turns plain-language feedback about a component inventory into structured correction instructions. A component inventory is a list of reusable parts found across a website or interface.

In plain words
What is it for?
Renaming, merging, splitting, or changing the type of component groups based on review feedback.
Why use it?
It removes the manual work of translating review comments into precise inventory changes.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the nextjs-migration-plugin plugin — 18 skills, 4 commands, 16 agents shipped together

Good fit Renaming, merging, splitting, or changing the type of component groups based on review feedback.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/blazity/nextjs-migration-plugin/inventory-corrector
Install

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.

Clone the repo
git clone --depth 1 https://github.com/Blazity/nextjs-migration-plugin

Made for: Claude Code.

Or install nextjs-migration-plugin, the plugin that ships this one along with the rest of its 18 skills, 4 commands, 16 agents.

Wrote 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.

agentmods badge for inventory-corrector

README.md
[![agentmods](https://agentmods.dev/badge/agents/blazity/nextjs-migration-plugin/inventory-corrector/github.svg)](https://agentmods.dev/agents/blazity/nextjs-migration-plugin/inventory-corrector)
Your own site
<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.

agentmods 80×15 button for inventory-corrector

Your own site · 80×15
<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>
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 496 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 1mo ago against content hash d326584b66f2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

agents/inventory-corrector.md · 53 lines

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 with componentGroupId, proposedName, kind, sectionInstanceIds, and optional notes.
  • 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

  1. Output JSON only: a top-level array matching InventoryCorrection[]; no prose, Markdown, or code fence.
  2. Use only group IDs and section instance IDs present in the provided inventory or context.
  3. Preserve raw discovery evidence. Corrections target draft inventory state only.
  4. Use semantic PascalCase component names for rename and split operations.
  5. Prefer no operation over guessing when the requested target cannot be identified.
  6. For merge, keep the most semantically accurate existing group as targetGroupId.
  7. 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.

Read the full file on GitHub · 53 lines

Changes

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.

  1. 1mo ago First seen · 53 lines · 18 tokens per session scan A d326584b66f2

Subscribe to this mod's changes

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.

Related

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.

HoangNguyen0403/agent-skills-standard · 66 tokens

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.

first-fluke/fullstack-starter · 33 tokens

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.…

gabelul/stitch-kit · 237 tokens

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…

sh5623/fe-rail · 85 tokens

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).…

sh5623/fe-rail · 90 tokens

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.

sh5623/fe-rail · 65 tokens