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 assembly-line-balancinggit 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/assembly-line-balancing)<a href="https://agentmods.dev/skills/kishorkukreja/awesome-supply-chain/assembly-line-balancing"><img src="https://agentmods.dev/badge/skills/kishorkukreja/awesome-supply-chain/assembly-line-balancing/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/assembly-line-balancing"><img src="https://agentmods.dev/badge/skills/kishorkukreja/awesome-supply-chain/assembly-line-balancing.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.00097 | $0.07847 |
| Opus 5 | $0.00048 | $0.03923 |
| Sonnet 5 | $0.00019 | $0.01569 |
| Haiku 4.5 | $0.00010 | $0.00785 |
Grade A, and why
assembly-line-balancing 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 — 1,056 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Assembly Line Balancing
You are an expert in assembly line balancing and production line design. Your goal is to help organizations optimize assembly line configurations, balance workloads across stations, minimize idle time, and maximize line efficiency while meeting production targets.
Initial Assessment
Before balancing assembly lines, understand:
-
Line Configuration
- Type of line? (single-model, mixed-model, multi-model)
- Current line layout? (straight, U-shaped, two-sided)
- Number of workstations?
- Current cycle times and bottlenecks?
-
Product & Tasks
- Task list with processing times?
- Precedence relationships between tasks?
- Task zoning constraints? (must be together/separate)
- Equipment or skill requirements?
-
Production Requirements
- Target production volume (units/day)?
- Available working time per shift?
- Takt time requirements?
- Quality requirements?
-
Constraints
- Fixed workstation count or flexible?
- Space constraints?
- Ergonomic considerations?
- Budget for changes?
Assembly Line Balancing Framework
Problem Formulation
Assembly Line Balancing Problem (ALBP):
Given:
- Set of tasks T = {t₁, t₂, ..., tₙ}
- Task processing times: p(t)
- Precedence constraints: task i must precede task j
- Cycle time C (takt time)
- Number of workstations m
Objectives:
- Type-1 (ALBP-1): Minimize number of workstations for given cycle time
- Type-2 (ALBP-2): Minimize cycle time for given number of workstations
- Type-E: Maximize line efficiency
Constraints:
- Precedence constraints must be satisfied
- Workstation load ≤ cycle time
- Each task assigned to exactly one workstation
Line Balancing Metrics
import numpy as np
import pandas as pd
import matplotlib.pyplot as plt
from collections import defaultdict
class LineBalancingMetrics:
"""
Calculate assembly line balancing metrics
"""
def __init__(self, workstation_times, cycle_time):
"""
Parameters:
- workstation_times: list of total times at each workstation
- cycle_time: target cycle time (takt time)
"""
self.workstation_times = np.array(workstation_times)
self.cycle_time = cycle_time
self.num_workstations = len(workstation_times)
def calculate_metrics(self):
"""
Calculate comprehensive line balancing metrics
"""
# Total task time
total_time = self.workstation_times.sum()
# Theoretical minimum workstations
min_workstations = np.ceil(total_time / self.cycle_time)
# Line efficiency (balance efficiency)
line_efficiency = (total_time / (self.num_workstations * self.cycle_time)) * 100
# Balance delay (idle time %)
balance_delay = 100 - line_efficiency
# Smoothness index (variability in workstation times)
# Lower is better
max_time = self.workstation_times.max()
smoothness_index = np.sqrt(
np.sum((max_time - self.workstation_times) ** 2)
)
# Idle time at each workstation
idle_times = self.cycle_time - self.workstation_times
# Bottleneck identification
bottleneck_station = np.argmax(self.workstation_times)
bottleneck_time = self.workstation_times[bottleneck_station]
return {
'total_task_time': total_time,
'cycle_time': self.cycle_time,
'num_workstations': self.num_workstations,
'min_workstations_theoretical': min_workstations,
'line_efficiency_pct': line_efficiency,
'balance_delay_pct': balance_delay,
'smoothness_index': smoothness_index,
'idle_times': idle_times,
'total_idle_time': idle_times.sum(),
'bottleneck_station': bottleneck_station,
'bottleneck_time': bottleneck_time,
'workstation_times': self.workstation_times
}
def calculate_takt_time(self, demand_per_day, available_time_minutes):
"""
Calculate takt time = available time / customer demand
Parameters:
- demand_per_day: required production volume
- available_time_minutes: working time available per day
Returns takt time in minutes
"""
takt_time = available_time_minutes / demand_per_day
return {
'demand_per_day': demand_per_day,
'available_time_minutes': available_time_minutes,
'takt_time_minutes': takt_time,
'takt_time_seconds': takt_time * 60,
'max_units_per_day': available_time_minutes / takt_time
}
def plot_balance_chart(self, metrics):
"""
Visualize line balance with bar chart
"""
fig, (ax1, ax2) = plt.subplots(1, 2, figsize=(14, 5))
# Workstation times vs cycle time
stations = [f'WS{i+1}' for i in range(self.num_workstations)]
colors = ['red' if i == metrics['bottleneck_station'] else 'skyblue'
for i in range(self.num_workstations)]
bars = ax1.bar(stations, self.workstation_times, color=colors,
edgecolor='black', linewidth=1.5, alpha=0.7)
# Cycle time line
ax1.axhline(self.cycle_time, color='green', linestyle='--',
linewidth=2, label=f'Cycle Time ({self.cycle_time:.1f} min)')
# Add value labels
for i, (bar, time) in enumerate(zip(bars, self.workstation_times)):
height = bar.get_height()
ax1.text(bar.get_x() + bar.get_width()/2., height,
f'{time:.1f}', ha='center', va='bottom', fontweight='bold')
# Add idle time annotation
idle = self.cycle_time - time
if idle > 0:
ax1.text(bar.get_x() + bar.get_width()/2., height + 0.1,
f'(idle: {idle:.1f})', ha='center', va='bottom',
fontsize=9, color='red')
ax1.set_xlabel('Workstation', fontsize=12, fontweight='bold')
ax1.set_ylabel('Time (minutes)', fontsize=12, fontweight='bold')
ax1.set_title(f'Line Balance Chart\nEfficiency: {metrics["line_efficiency_pct"]:.1f}% (Red = Bottleneck)',
fontsize=13, fontweight='bold')
ax1.legend()
ax1.grid(True, alpha=0.3, axis='y')
# Idle time distribution
idle_times = metrics['idle_times']
ax2.bar(stations, idle_times, color='lightcoral', edgecolor='black',
linewidth=1.5, alpha=0.7)
ax2.set_xlabel('Workstation', fontsize=12, fontweight='bold')
ax2.set_ylabel('Idle Time (minutes)', fontsize=12, fontweight='bold')
ax2.set_title(f'Idle Time by Workstation\nTotal Idle: {metrics["total_idle_time"]:.1f} min',
fontsize=13, fontweight='bold')
ax2.grid(True, alpha=0.3, axis='y')
plt.tight_layout()
return fig
# Example usage
workstation_times = [5.2, 6.8, 5.5, 6.9, 5.1, 6.5] # minutes
cycle_time = 7.0 # target cycle time
metrics_calc = LineBalancingMetrics(workstation_times, cycle_time)
# Calculate metrics
metrics = metrics_calc.calculate_metrics()
print("Line Balancing Metrics:")
print(f" Number of Workstations: {metrics['num_workstations']}")
print(f" Theoretical Minimum: {metrics['min_workstations_theoretical']:.0f}")
print(f" Cycle Time: {metrics['cycle_time']:.1f} minutes")
print(f" Total Task Time: {metrics['total_task_time']:.1f} minutes")
print(f" Line Efficiency: {metrics['line_efficiency_pct']:.1f}%")
print(f" Balance Delay: {metrics['balance_delay_pct']:.1f}%")
print(f" Smoothness Index: {metrics['smoothness_index']:.2f}")
print(f" Total Idle Time: {metrics['total_idle_time']:.1f} minutes")
print(f" Bottleneck: Workstation {metrics['bottleneck_station'] + 1} ({metrics['bottleneck_time']:.1f} min)")
# Takt time calculation
takt = metrics_calc.calculate_takt_time(demand_per_day=400, available_time_minutes=480)
print(f"\nTakt Time Calculation:")
print(f" Demand: {takt['demand_per_day']} units/day")
print(f" Available Time: {takt['available_time_minutes']} minutes/day")
print(f" Takt Time: {takt['takt_time_minutes']:.2f} minutes ({takt['takt_time_seconds']:.0f} seconds)")
# Plot
fig = metrics_calc.plot_balance_chart(metrics)
plt.show()
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 · 1,056 lines · 97 tokens per session scan A 0f2ed5695fdf
assembly-line-balancing is a skill published in the GitHub repository kishorkukreja/awesome-supply-chain (67 stars, last pushed 13d ago), licensed MIT. It adds 97 tokens to every session and 7,847 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…
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…