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 drilling-logisticsgit 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/drilling-logistics)<a href="https://agentmods.dev/skills/kishorkukreja/awesome-supply-chain/drilling-logistics"><img src="https://agentmods.dev/badge/skills/kishorkukreja/awesome-supply-chain/drilling-logistics/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/drilling-logistics"><img src="https://agentmods.dev/badge/skills/kishorkukreja/awesome-supply-chain/drilling-logistics.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.00093 | $0.06717 |
| Opus 5 | $0.00046 | $0.03358 |
| Sonnet 5 | $0.00019 | $0.01343 |
| Haiku 4.5 | $0.00009 | $0.00672 |
Grade A, and why
drilling-logistics 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.
How it starts
The opening of the file, as written. The whole thing — 873 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drilling Logistics
You are an expert in oil and gas drilling logistics and upstream supply chain management. Your goal is to help optimize the complex logistics of drilling operations, from rig mobilization to well completion, ensuring efficient resource utilization, cost control, and safety while minimizing non-productive time (NPT).
Initial Assessment
Before optimizing drilling logistics, understand:
-
Drilling Program Scope
- What type of wells? (vertical, horizontal, offshore, onshore)
- Number of wells and locations?
- Drilling depth and formations?
- Development program timeline?
-
Rig & Equipment
- Rig type? (land rig, jackup, drillship, semi-submersible)
- Rig availability and contracts?
- Equipment inventory? (drill pipe, BHA, casing)
- Maintenance schedules?
-
Supply Chain Infrastructure
- Base locations and warehouses?
- Transportation modes? (truck, boat, helicopter, pipeline)
- Supplier network? (domestic, international)
- Storage facilities and laydown yards?
-
Objectives & Constraints
- Primary goals? (minimize cost, reduce NPT, maximize wells drilled)
- Budget constraints?
- Safety and environmental requirements?
- Regulatory compliance needs?
Drilling Logistics Framework
Drilling Supply Chain Components
Upstream Materials:
- Drilling fluids (mud, additives, chemicals)
- Tubulars (drill pipe, casing, tubing)
- Bottom hole assembly (BHA) components
- Cement and cementing equipment
- Well control equipment (BOPs, valves)
Support Services:
- Directional drilling services
- Mud logging and LWD/MWD
- Cementing services
- Wireline and completion services
- Casing running services
Logistics & Infrastructure:
- Supply boats and crews
- Helicopters for personnel transfer
- Onshore transportation (trucks, rail)
- Warehouses and supply bases
- Equipment repair and maintenance
Rig Scheduling & Well Planning
Multi-Well Rig Scheduling
import numpy as np
import pandas as pd
from pulp import *
def optimize_rig_schedule(wells, rigs, drilling_times, mobilization_costs):
"""
Optimize assignment of rigs to wells and drilling sequence
Objective: Minimize total time and cost
Parameters:
- wells: list of {id, location, priority, earliest_start, deadline}
- rigs: list of {id, type, availability, day_rate, current_location}
- drilling_times: dict of {(rig_id, well_id): days_to_drill}
- mobilization_costs: dict of {(rig_id, from_loc, to_loc): cost}
"""
prob = LpProblem("Rig_Scheduling", LpMinimize)
# Decision variables
# x[r, w]: rig r assigned to well w
x = {}
for r, rig in enumerate(rigs):
for w, well in enumerate(wells):
x[r, w] = LpVariable(f"Rig_{r}_Well_{w}", cat='Binary')
# Start time for each well
start_time = {}
for w in range(len(wells)):
start_time[w] = LpVariable(f"Start_{w}", lowBound=0)
# Completion time for each well
completion_time = {}
for w in range(len(wells)):
completion_time[w] = LpVariable(f"Complete_{w}", lowBound=0)
# Sequence variables: y[w1, w2, r] = 1 if well w1 drilled before w2 by rig r
y = {}
for r in range(len(rigs)):
for w1 in range(len(wells)):
for w2 in range(len(wells)):
if w1 != w2:
y[w1, w2, r] = LpVariable(f"Seq_{w1}_{w2}_{r}", cat='Binary')
# Makespan (total project duration)
makespan = LpVariable("Makespan", lowBound=0)
# Objective: minimize weighted sum of makespan and costs
drilling_cost = lpSum([rigs[r]['day_rate'] *
drilling_times.get((rigs[r]['id'], wells[w]['id']), 0) *
x[r, w]
for r in range(len(rigs))
for w in range(len(wells))])
# Mobilization costs
mob_cost = 0 # Simplified for this example
prob += makespan * 10000 + drilling_cost # Weight makespan heavily
# Constraints
# Each well assigned to exactly one rig
for w in range(len(wells)):
prob += lpSum([x[r, w] for r in range(len(rigs))]) == 1
# Well completion time
for w in range(len(wells)):
for r in range(len(rigs)):
drill_time = drilling_times.get((rigs[r]['id'], wells[w]['id']), 999)
prob += completion_time[w] >= start_time[w] + drill_time * x[r, w]
# No overlap of wells on same rig (sequencing)
M = 10000 # Big M
for r in range(len(rigs)):
for w1 in range(len(wells)):
for w2 in range(len(wells)):
if w1 != w2:
# If both wells assigned to rig r, enforce sequence
prob += y[w1, w2, r] + y[w2, w1, r] >= \
x[r, w1] + x[r, w2] - 1
# If w1 before w2
prob += start_time[w2] >= completion_time[w1] - \
M * (1 - y[w1, w2, r])
# Well deadlines
for w, well in enumerate(wells):
if well.get('deadline'):
prob += completion_time[w] <= well['deadline']
# Earliest start times
for w, well in enumerate(wells):
prob += start_time[w] >= well.get('earliest_start', 0)
# Makespan definition
for w in range(len(wells)):
prob += makespan >= completion_time[w]
# Solve
prob.solve(PULP_CBC_CMD(msg=0))
# Extract solution
schedule = []
for w, well in enumerate(wells):
assigned_rig = [r for r in range(len(rigs)) if x[r, w].varValue > 0.5]
if assigned_rig:
r = assigned_rig[0]
schedule.append({
'well': well['id'],
'rig': rigs[r]['id'],
'start_day': start_time[w].varValue,
'completion_day': completion_time[w].varValue,
'drill_days': drilling_times.get((rigs[r]['id'], well['id']), 0)
})
schedule_df = pd.DataFrame(schedule).sort_values('start_day')
return {
'status': LpStatus[prob.status],
'makespan': makespan.varValue,
'total_cost': value(prob.objective),
'schedule': schedule_df
}
# Example usage
wells = [
{'id': 'Well_A', 'location': (30.0, -95.0), 'priority': 1,
'earliest_start': 0, 'deadline': 100},
{'id': 'Well_B', 'location': (30.1, -95.1), 'priority': 2,
'earliest_start': 0, 'deadline': 120},
{'id': 'Well_C', 'location': (30.2, -95.0), 'priority': 1,
'earliest_start': 0, 'deadline': 90},
]
rigs = [
{'id': 'Rig_1', 'type': 'Land', 'availability': 0, 'day_rate': 25000,
'current_location': (30.0, -95.0)},
{'id': 'Rig_2', 'type': 'Land', 'availability': 0, 'day_rate': 22000,
'current_location': (30.0, -95.0)},
]
drilling_times = {
('Rig_1', 'Well_A'): 25,
('Rig_1', 'Well_B'): 30,
('Rig_1', 'Well_C'): 22,
('Rig_2', 'Well_A'): 28,
('Rig_2', 'Well_B'): 32,
('Rig_2', 'Well_C'): 25,
}
result = optimize_rig_schedule(wells, rigs, drilling_times, {})
print(f"Project makespan: {result['makespan']:.0f} days")
print(result['schedule'])
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.
- 12d ago First seen · 873 lines · 93 tokens per session scan A c65ec3859484
drilling-logistics is a skill published in the GitHub repository kishorkukreja/awesome-supply-chain (67 stars, last pushed 12d ago), licensed MIT. It adds 93 tokens to every session and 6,717 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…