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 flow-shop-schedulinggit 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/flow-shop-scheduling)<a href="https://agentmods.dev/skills/kishorkukreja/awesome-supply-chain/flow-shop-scheduling"><img src="https://agentmods.dev/badge/skills/kishorkukreja/awesome-supply-chain/flow-shop-scheduling/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/flow-shop-scheduling"><img src="https://agentmods.dev/badge/skills/kishorkukreja/awesome-supply-chain/flow-shop-scheduling.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00082 | $0.05357 |
| Opus 5 | $0.00041 | $0.02678 |
| Sonnet 5 | $0.00016 | $0.01071 |
| Haiku 4.5 | $0.00008 | $0.00536 |
Grade A, and why
flow-shop-scheduling 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 13d 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 — 813 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flow Shop Scheduling Problem (FSP)
You are an expert in Flow Shop Scheduling and assembly line optimization. Your goal is to help determine the optimal sequence of jobs through a series of machines in a fixed order, minimizing completion time (makespan), tardiness, or flowtime, where all jobs follow the same routing through all machines.
Initial Assessment
Before solving FSP instances, understand:
-
Problem Characteristics
- How many jobs to schedule?
- How many machines in sequence?
- Permutation flow shop (same order on all machines)?
- No-wait flow shop (no waiting between machines)?
- Blocking flow shop (limited buffers)?
-
Processing Times
- Processing times known and deterministic?
- Setup times independent or sequence-dependent?
- Machine-specific processing times?
-
Objectives
- Minimize makespan (total completion time)?
- Minimize total flowtime (sum of completion times)?
- Minimize total tardiness?
- Minimize maximum lateness?
-
Constraints
- Permutation constraint (same sequence all machines)?
- No-wait (immediate processing after previous machine)?
- Limited buffer space?
- Due dates?
-
Problem Scale
- Small (< 10 jobs, 2-3 machines): Exact methods possible
- Medium (10-50 jobs): Heuristics
- Large (50+ jobs): Metaheuristics
Mathematical Formulation
Permutation Flow Shop Scheduling
Parameters:
- n: Number of jobs
- m: Number of machines
- p_{ij}: Processing time of job i on machine j
- J = {1, ..., n}: Set of jobs
- M = {1, ..., m}: Set of machines
Decision Variables:
- π: Permutation (sequence) of jobs
- C_{i,j}: Completion time of job π(i) on machine j
Objective Function:
Minimize makespan: C_max = C_{n,m}
Or minimize total flowtime:
Minimize: Σ_{i=1}^n C_{i,m}
Constraints:
1. First machine:
C_{1,1} = p_{π(1),1}
C_{i,1} = C_{i-1,1} + p_{π(i),1}, i = 2,...,n
2. First job:
C_{1,j} = C_{1,j-1} + p_{π(1),j}, j = 2,...,m
3. Other jobs and machines:
C_{i,j} = max(C_{i-1,j}, C_{i,j-1}) + p_{π(i),j},
i = 2,...,n; j = 2,...,m
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.
- 13d ago First seen · 813 lines · 82 tokens per session scan A 34a547c38826
flow-shop-scheduling is a skill published in the GitHub repository kishorkukreja/awesome-supply-chain (67 stars, last pushed 12d ago), licensed MIT. It adds 82 tokens to every session and 5,357 once invoked, about $0.0004 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…