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 skills add kishorkukreja/awesome-supply-chain --skill facility-location-problemgit clone --depth 1 https://github.com/kishorkukreja/awesome-supply-chainWrote 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/skills/kishorkukreja/awesome-supply-chain/facility-location-problem)<a href="https://agentmods.dev/skills/kishorkukreja/awesome-supply-chain/facility-location-problem"><img src="https://agentmods.dev/badge/skills/kishorkukreja/awesome-supply-chain/facility-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.
<a href="https://agentmods.dev/skills/kishorkukreja/awesome-supply-chain/facility-location-problem"><img src="https://agentmods.dev/badge/skills/kishorkukreja/awesome-supply-chain/facility-location-problem.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
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 contentFix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
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.00107 | $0.11841 |
| Opus 5 | $0.00053 | $0.05921 |
| Sonnet 5 | $0.00021 | $0.02368 |
| Haiku 4.5 | $0.00011 | $0.01184 |
Grade A, and why
facility-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 11d 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 — 1,634 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Facility Location Problem (FLP)
You are an expert in facility location problems and strategic site selection optimization. Your goal is to help determine optimal locations for facilities (warehouses, plants, distribution centers) to minimize total costs while meeting customer demand and capacity constraints.
Initial Assessment
Before solving facility location problems, understand:
-
Problem Type
- Uncapacitated Facility Location (UFLP)? (no capacity limits)
- Capacitated Facility Location (CFLP)? (facilities have capacity limits)
- p-Median Problem? (locate exactly p facilities)
- p-Center Problem? (minimize maximum distance)
- Fixed Charge Location? (fixed opening costs + variable costs)
-
Facility Characteristics
- How many potential facility locations?
- Fixed opening costs per facility?
- Operating costs (capacity-dependent)?
- Facility capacities (if capacitated)?
- Can facilities serve multiple customers?
-
Customer Requirements
- How many customers/demand points?
- Customer demands (quantities)?
- Service requirements (coverage distance/time)?
- Single-sourcing or multi-sourcing allowed?
-
Cost Structure
- Fixed costs to open facilities?
- Transportation/distribution costs?
- Operating costs per unit shipped?
- Economies of scale?
-
Constraints
- Must open exactly p facilities? (p-median)
- Budget constraints?
- Capacity constraints?
- Coverage requirements?
- Minimum/maximum number of facilities?
Problem Classification
1. Uncapacitated Facility Location Problem (UFLP)
Description:
- Decide which facilities to open (no capacity limits)
- Assign customers to open facilities
- Minimize total fixed + transportation costs
Characteristics:
- Each facility can serve unlimited demand
- Most basic FLP variant
- NP-hard but solvable for moderate instances
Applications:
- Initial network design
- Strategic long-term planning
- High-level site selection
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.
- 11d ago First seen · 1,634 lines · 107 tokens per session scan A c87c5e10b903
facility-location-problem is a skill published in the GitHub repository kishorkukreja/awesome-supply-chain (67 stars, last pushed 11d ago), licensed MIT. It adds 107 tokens to every session and 11,841 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
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…