hub-location-problem

hub-location-problem is a skill for Claude Code from kishorkukreja/awesome-supply-chain. It costs 104 tokens per session (9,036 once invoked), scanned A, original, MIT.

A planning tool for choosing hub facilities in a transport network. A hub-and-spoke network routes shipments or other flows through central facilities, and hub-location problems determine where those facilities should be placed.

In plain words
What is it for?
Use it to design logistics or airline-style hub networks, choose a specified number of hubs, assign nodes to one or more hubs, and account for demand, capacities, fixed costs, and routing objectives.
Why use it?
It helps structure decisions about facility placement, routing, capacity, costs, and how locations connect to hubs. This reduces the need to formulate the network problem from scratch.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: positional $N argument.

Part of the supply-chain-skills plugin — 133 skills shipped together , and of supply-chain-skills

Good fit Use it to design logistics or airline-style hub networks, choose a specified number of hubs, assign nodes to one or more hubs, and account for demand, capacities, fixed costs, and routing objectives.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kishorkukreja/awesome-supply-chain/hub-location-problem
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 kishorkukreja/awesome-supply-chain --skill hub-location-problem
Clone the repo
git clone --depth 1 https://github.com/kishorkukreja/awesome-supply-chain

Made for: Claude Code.

Or install supply-chain-skills, the plugin that ships this one along with the rest of its 133 skills.

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 hub-location-problem

README.md
[![agentmods](https://agentmods.dev/badge/skills/kishorkukreja/awesome-supply-chain/hub-location-problem/github.svg)](https://agentmods.dev/skills/kishorkukreja/awesome-supply-chain/hub-location-problem)
Your own site
<a href="https://agentmods.dev/skills/kishorkukreja/awesome-supply-chain/hub-location-problem"><img src="https://agentmods.dev/badge/skills/kishorkukreja/awesome-supply-chain/hub-location-problem/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 hub-location-problem

Your own site · 80×15
<a href="https://agentmods.dev/skills/kishorkukreja/awesome-supply-chain/hub-location-problem"><img src="https://agentmods.dev/badge/skills/kishorkukreja/awesome-supply-chain/hub-location-problem.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 104 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 9,036 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium analysis-evasion · line 1
    Suspicious Unicode normalization or mixed-script content
    Fix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
How audits are shown
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.00104 $0.09036
Opus 5 $0.00052 $0.04518
Sonnet 5 $0.00021 $0.01807
Haiku 4.5 $0.00010 $0.00904

Measured 12d ago against content hash 0c454b921a61, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

hub-location-problem 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 12d 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.

skills/hub-location-problem/SKILL.md · 1,266 lines

How it starts

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

Hub Location Problem

You are an expert in hub location problems and hub-and-spoke network design. Your goal is to help design efficient hub-and-spoke networks where flows between origin-destination pairs are consolidated through hub facilities, minimizing total transportation and routing costs.

Initial Assessment

Before solving hub location problems, understand:

  1. Network Type

    • Hub-and-spoke network? (consolidation through hubs)
    • How many hubs to locate? (p-hub problem)
    • Hub covering problem? (coverage requirements)
    • Hub hierarchy? (multi-level hubs)
  2. Allocation Type

    • Single allocation? (each node assigned to exactly one hub)
    • Multiple allocation? (nodes can connect to multiple hubs)
    • r-allocation? (each node connects to at most r hubs)
  3. Flow Characteristics

    • Origin-destination (O-D) flow matrix?
    • Demand between all pairs?
    • Flow volumes/patterns?
    • Directionality (symmetric or asymmetric)?
  4. Hub Characteristics

    • Hub capacity constraints?
    • Fixed costs to establish hubs?
    • Hub processing/handling costs?
    • Economies of scale at hubs?
    • Discount factor (α) for inter-hub connections?
  5. Network Objectives

    • Minimize total transportation cost?
    • Minimize maximum travel time? (p-hub center)
    • Minimize number of hubs?
    • Balance hub loads?

Hub Location Problem Framework

Hub-and-Spoke Network Concept

Structure:

Origin → Access Hub → Hub-to-Hub → Egress Hub → Destination

Collection   |  Consolidation  |   Distribution
   Leg       |      Leg        |      Leg

Key Features:

  • Consolidation: Flows between O-D pairs routed through hubs
  • Economies of Scale: Inter-hub transport cheaper (discount factor α)
  • Hub Facilities: Special facilities with sorting/consolidation capability
  • Reduced Connections: Not all nodes directly connected

Applications:

  • Airline passenger networks
  • Cargo/freight networks
  • Postal/package delivery
  • Telecommunications networks
  • Supply chain distribution
  • Public transportation

Read the full file on GitHub · 1,266 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. 12d ago First seen · 1,266 lines · 104 tokens per session scan A 0c454b921a61

Subscribe to this mod's changes

hub-location-problem is a skill published in the GitHub repository kishorkukreja/awesome-supply-chain (67 stars, last pushed 12d ago), licensed MIT. It adds 104 tokens to every session and 9,036 once invoked, about $0.0005 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-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens