inventory-demand-planning

inventory-demand-planning is a skill for Claude Code from multiplex-ai/muggle-ai-teams. It costs 86 tokens per session (5,451 once invoked), scanned A, a copy of inventory-demand-planning, MIT.

A set of methods for predicting product demand and planning inventory across multiple stores and distribution centres. It covers safety stock, replenishment, seasonal changes, promotions, and new products.

In plain words
What is it for?
Use it to choose forecasting methods, analyse products by demand and predictability, set safety stock, plan replenishment, and review forecast accuracy.
Why use it?
It helps reduce empty shelves and excess stock by connecting expected sales with purchasing and warehouse decisions.

Skill for Claude Code

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

Part of the muggle-ai-teams plugin — 166 skills, 55 commands, 30 agents, 4 hooks shipped together

Good fit Use it to choose forecasting methods, analyse products by demand and predictability, set safety stock, plan replenishment, and review forecast accuracy.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/multiplex-ai/muggle-ai-teams/inventory-demand-planning
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.

Any agent
npx skills add multiplex-ai/muggle-ai-teams --skill inventory-demand-planning
Clone the repo
git clone --depth 1 https://github.com/multiplex-ai/muggle-ai-teams

Made for: Claude Code.

Or install muggle-ai-teams, the plugin that ships this one along with the rest of its 166 skills, 55 commands, 30 agents, 4 hooks.

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-demand-planning

README.md
[![agentmods](https://agentmods.dev/badge/skills/multiplex-ai/muggle-ai-teams/inventory-demand-planning/github.svg)](https://agentmods.dev/skills/multiplex-ai/muggle-ai-teams/inventory-demand-planning)
Your own site
<a href="https://agentmods.dev/skills/multiplex-ai/muggle-ai-teams/inventory-demand-planning"><img src="https://agentmods.dev/badge/skills/multiplex-ai/muggle-ai-teams/inventory-demand-planning/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-demand-planning

Your own site · 80×15
<a href="https://agentmods.dev/skills/multiplex-ai/muggle-ai-teams/inventory-demand-planning"><img src="https://agentmods.dev/badge/skills/multiplex-ai/muggle-ai-teams/inventory-demand-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 86 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,451 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 100% copy Near-identical to another mod 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.00086 $0.05451
Opus 5.5 $0.00034 $0.02180
Sonnet 5.5 $0.00017 $0.01090
Haiku 4.5 $0.00009 $0.00545

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

Security

Grade A, and why

inventory-demand-planning 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 6d 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.

Origin

This is a copy

100% identical to inventory-demand-planning — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/inventory-demand-planning/SKILL.md · 248 lines

How it starts

The opening of the file, as written. The whole thing — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Inventory Demand Planning

Role and Context

You are a senior demand planner at a multi-location retailer operating 40–200 stores with regional distribution centers. You manage 300–800 active SKUs across categories including grocery, general merchandise, seasonal, and promotional assortments. Your systems include a demand planning suite (Blue Yonder, Oracle Demantra, or Kinaxis), an ERP (SAP, Oracle), a WMS for DC-level inventory, POS data feeds at the store level, and vendor portals for purchase order management. You sit between merchandising (which decides what to sell and at what price), supply chain (which manages warehouse capacity and transportation), and finance (which sets inventory investment budgets and GMROI targets). Your job is to translate commercial intent into executable purchase orders while minimizing both stockouts and excess inventory.

When to Use

  • Generating or reviewing demand forecasts for existing or new SKUs
  • Setting safety stock levels based on demand variability and service level targets
  • Planning replenishment for seasonal transitions, promotions, or new product launches
  • Evaluating forecast accuracy and adjusting models or overrides
  • Making buy decisions under supplier MOQ constraints or lead time changes

How It Works

  1. Collect demand signals (POS sell-through, orders, shipments) and cleanse outliers
  2. Select forecasting method per SKU based on ABC/XYZ classification and demand pattern
  3. Apply promotional lifts, cannibalization offsets, and external causal factors
  4. Calculate safety stock using demand variability, lead time variability, and target fill rate
  5. Generate suggested purchase orders, apply MOQ/EOQ rounding, and route for planner review
  6. Monitor forecast accuracy (MAPE, bias) and adjust models in the next planning cycle

Examples

  • Seasonal promotion planning: Merchandising plans a 3-week BOGO promotion on a top-20 SKU. Estimate promotional lift using historical promo elasticity, calculate the forward buy quantity, coordinate with the vendor on advance PO and logistics capacity, and plan the post-promo demand dip.
  • New SKU launch: No demand history available. Use analog SKU mapping (similar category, price point, brand) to generate an initial forecast, set conservative safety stock at 2 weeks of projected sales, and define the review cadence for the first 8 weeks.
  • DC replenishment under lead time change: Key vendor extends lead time from 14 to 21 days due to port congestion. Recalculate safety stock across all affected SKUs, identify which are at risk of stockout before the new POs arrive, and recommend bridge orders or substitute sourcing.

Read the full file on GitHub · 248 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. 6d ago First seen · 248 lines · 86 tokens per session scan A e8ccbdc15eb3

Subscribe to this mod's changes

inventory-demand-planning is a skill published in the GitHub repository multiplex-ai/muggle-ai-teams (2 stars, last pushed 2d ago), licensed MIT. It adds 86 tokens to every session and 5,451 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to inventory-demand-planning, differing in 2 lines, and is treated as a copy.