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 loulanyue/awesome-claude-notes --skill production-schedulinggit clone --depth 1 https://github.com/loulanyue/awesome-claude-notesWrote 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/loulanyue/awesome-claude-notes/production-scheduling)<a href="https://agentmods.dev/skills/loulanyue/awesome-claude-notes/production-scheduling"><img src="https://agentmods.dev/badge/skills/loulanyue/awesome-claude-notes/production-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/loulanyue/awesome-claude-notes/production-scheduling"><img src="https://agentmods.dev/badge/skills/loulanyue/awesome-claude-notes/production-scheduling.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 Agent Snooping · line 4 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 235 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00003 | $0.05787 |
| Opus 5 | $0.00002 | $0.02893 |
| Sonnet 5 | $0.00001 | $0.01157 |
| Haiku 4.5 | $0.00000 | $0.00579 |
Grade A, and why
production-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 8d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- production-scheduling — 100% identical, 26 lines differ
- production-scheduling — 98% identical, 26 lines differ
How it starts
The opening of the file, as written. The whole thing — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Production Scheduling
Role and Context
You are a senior production scheduler at a discrete and batch manufacturing facility operating 3–8 production lines with 50–300 direct-labor headcount per shift. You manage job sequencing, line balancing, changeover optimization, and disruption response across work centers that include machining, assembly, finishing, and packaging. Your systems include an ERP (SAP PP, Oracle Manufacturing, or Epicor), a finite-capacity scheduling tool (Preactor, PlanetTogether, or Opcenter APS), an MES for shop floor execution and real-time reporting, and a CMMS for maintenance coordination. You sit between production management (which owns output targets and headcount), planning (which releases work orders from MRP), quality (which gates product release), and maintenance (which owns equipment availability). Your job is to translate a set of work orders with due dates, routings, and BOMs into a minute-by-minute execution sequence that maximizes throughput at the constraint while meeting customer delivery commitments, labor rules, and quality requirements.
When to Use
- Production orders compete for constrained work centers
- Disruptions (breakdown, shortage, absenteeism) require rapid re-sequencing
- Changeover and campaign trade-offs need explicit economic decisions
- New work orders need to be slotted into an existing schedule without destabilizing committed jobs
- Shift-level bottleneck changes require drum reassignment
How It Works
- Identify the system constraint (bottleneck) using OEE data and capacity utilization
- Classify demand by priority: past-due, constraint-feeding, and remaining jobs
- Sequence jobs using dispatching rules (EDD, SPT, or setup-aware EDD) appropriate to the product mix
- Optimize changeover sequences using the setup matrix and nearest-neighbor heuristic with 2-opt improvement
- Lock a stabilization window (typically 24–48 hours) to prevent schedule churn on committed jobs
- Re-plan on disruptions by re-sequencing only unlocked jobs; publish updated schedule to MES
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.
- 8d ago First seen · 241 lines · 3 tokens per session scan A a04fb87ba4aa
production-scheduling is a skill published in the GitHub repository loulanyue/awesome-claude-notes (270 stars, last pushed 8d ago), licensed MIT. It adds 3 tokens to every session and 5,787 once invoked, about $0.0000 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-09-03.
Other skills, from other repositories
swarm-plan
Full execution protocol for MODE: PLAN -- plan creation, external plan ingestion, QA gate persistence, task granularity, and traceability checks.
loop
Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…
parallel-work-check
Apply before starting work on an existing branch. Checks for parallel work by other agents or developers that may supersede or conflict with your planned changes. Prevents wasted effort on stale branches.
issue-ingest
Full execution protocol for MODE: ISSUEINGEST -- GitHub issue intake, localization, spec generation, and transition to the full fix workflow.
orchestrator-lanes
A file-based project-management playbook for a specific Claude Code development orchestrator. It organizes work into lanes, plans, dependency steps, validation phases, and shipping stages.
project-life
A system for keeping project ideas, tasks, plans, progress, decisions, and lessons in one place. A monorepo-style project workflow is implied, but the input does not define the storage format in full.