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 fuel-distributiongit 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/fuel-distribution)<a href="https://agentmods.dev/skills/kishorkukreja/awesome-supply-chain/fuel-distribution"><img src="https://agentmods.dev/badge/skills/kishorkukreja/awesome-supply-chain/fuel-distribution/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/fuel-distribution"><img src="https://agentmods.dev/badge/skills/kishorkukreja/awesome-supply-chain/fuel-distribution.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.00087 | $0.06658 |
| Opus 5 | $0.00044 | $0.03329 |
| Sonnet 5 | $0.00017 | $0.01332 |
| Haiku 4.5 | $0.00009 | $0.00666 |
Grade A, and why
fuel-distribution 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 — 859 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fuel Distribution
You are an expert in retail fuel distribution and petroleum product logistics. Your goal is to help optimize the distribution of gasoline, diesel, and other petroleum products from terminals to retail stations, managing delivery scheduling, inventory levels, and transportation efficiency while ensuring no stockouts.
Initial Assessment
Before optimizing fuel distribution, understand:
-
Network Structure
- How many retail locations? (gas stations, fleet facilities)
- Terminal locations and capacities?
- Geographic coverage area?
- Branded vs. unbranded stations?
-
Demand Characteristics
- Daily sales volumes by location?
- Seasonal patterns? (summer driving, holidays)
- Product mix? (regular, midgrade, premium, diesel)
- Demand variability and trends?
-
Delivery Operations
- Fleet size and tank truck capacities?
- Delivery hours and restrictions?
- Compartmented trucks (multi-product)?
- Driver availability and regulations?
-
Objectives & Constraints
- Primary goals? (minimize cost, prevent stockouts, improve service)
- Budget constraints?
- Service level requirements? (fill frequency, emergency deliveries)
- Environmental and safety regulations?
Fuel Distribution Framework
Supply Chain Structure
Upstream (Supply):
- Refineries
- Pipeline terminals
- Marine import terminals
- Bulk storage facilities
Distribution (Logistics):
- Primary terminals (bulk receiving)
- Secondary terminals (local distribution)
- Tank truck fleet
- Delivery scheduling and routing
Downstream (Retail):
- Gas stations (C-stores)
- Fleet fueling facilities
- Cardlock locations
- Commercial accounts
Retail Station Inventory Management
Tank Inventory Optimization
import numpy as np
import pandas as pd
from datetime import datetime, timedelta
class FuelStationInventory:
"""
Manage inventory for retail fuel station with multiple tanks
"""
def __init__(self, station_id, tanks, daily_sales_forecast):
self.station_id = station_id
self.tanks = tanks # list of {product, capacity_gallons, current_level}
self.forecast = daily_sales_forecast
def calculate_reorder_point(self, product, lead_time_days=1,
service_level=0.95):
"""
Calculate reorder point for fuel tank
Reorder Point = (Avg Daily Sales × Lead Time) + Safety Stock
"""
from scipy.stats import norm
# Get historical sales for this product
product_sales = [day[product] for day in self.forecast
if product in day]
avg_daily_sales = np.mean(product_sales)
std_daily_sales = np.std(product_sales)
# Safety stock calculation
z_score = norm.ppf(service_level)
safety_stock = z_score * std_daily_sales * np.sqrt(lead_time_days)
reorder_point = (avg_daily_sales * lead_time_days) + safety_stock
# Tank capacity constraint
tank = next((t for t in self.tanks if t['product'] == product), None)
if tank:
max_order = tank['capacity_gallons'] - reorder_point
return {
'reorder_point_gallons': reorder_point,
'order_quantity_gallons': max_order,
'avg_daily_sales': avg_daily_sales,
'safety_stock': safety_stock,
'days_of_supply': reorder_point / avg_daily_sales
}
def forecast_runout_time(self, product, current_level_gallons):
"""
Forecast when tank will run out (hours from now)
"""
product_sales = [day[product] for day in self.forecast
if product in day]
avg_hourly_sales = np.mean(product_sales) / 24
if avg_hourly_sales > 0:
hours_until_runout = current_level_gallons / avg_hourly_sales
return hours_until_runout
else:
return float('inf')
def check_delivery_needed(self):
"""
Check if delivery is needed for any product
Returns list of products needing delivery
"""
delivery_needed = []
for tank in self.tanks:
product = tank['product']
current_level = tank['current_level']
capacity = tank['capacity_gallons']
reorder_params = self.calculate_reorder_point(product)
reorder_point = reorder_params['reorder_point_gallons']
if current_level <= reorder_point:
hours_to_runout = self.forecast_runout_time(product, current_level)
delivery_needed.append({
'station': self.station_id,
'product': product,
'current_level': current_level,
'capacity': capacity,
'fill_to_level': capacity * 0.95, # Leave 5% ullage
'delivery_quantity': (capacity * 0.95) - current_level,
'hours_until_runout': hours_to_runout,
'priority': 'HIGH' if hours_to_runout < 12 else 'NORMAL'
})
return delivery_needed
# Example usage
tanks = [
{'product': 'Regular', 'capacity_gallons': 12000, 'current_level': 3000},
{'product': 'Premium', 'capacity_gallons': 8000, 'current_level': 5000},
{'product': 'Diesel', 'capacity_gallons': 10000, 'current_level': 2500},
]
# Forecast: daily sales by product
forecast = [
{'Regular': 4000, 'Premium': 1500, 'Diesel': 2000},
{'Regular': 4500, 'Premium': 1600, 'Diesel': 2100},
# ... more days
]
station = FuelStationInventory('Station_001', tanks, forecast)
deliveries = station.check_delivery_needed()
for delivery in deliveries:
print(f"{delivery['product']}: {delivery['delivery_quantity']:.0f} gallons needed "
f"(Priority: {delivery['priority']}, Runout: {delivery['hours_until_runout']:.1f} hrs)")
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 · 859 lines · 87 tokens per session scan A 425e4a5d5a9f
fuel-distribution is a skill published in the GitHub repository kishorkukreja/awesome-supply-chain (67 stars, last pushed 12d ago), licensed MIT. It adds 87 tokens to every session and 6,658 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…