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 anhnguyen0905/codex-mcp --skill manufacturing-ops-planninggit clone --depth 1 https://github.com/anhnguyen0905/codex-mcpWrote 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/anhnguyen0905/codex-mcp/manufacturing-ops-planning)<a href="https://agentmods.dev/skills/anhnguyen0905/codex-mcp/manufacturing-ops-planning"><img src="https://agentmods.dev/badge/skills/anhnguyen0905/codex-mcp/manufacturing-ops-planning/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/anhnguyen0905/codex-mcp/manufacturing-ops-planning"><img src="https://agentmods.dev/badge/skills/anhnguyen0905/codex-mcp/manufacturing-ops-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00092 | $0.01108 |
| Opus 5 | $0.00046 | $0.00554 |
| Sonnet 5 | $0.00018 | $0.00222 |
| Haiku 4.5 | $0.00009 | $0.00111 |
Grade A, and why
manufacturing-ops-planning 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 11d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manufacturing Ops Planning (capacity, maintenance, shifts, cycle time)
Definitions — compute these before recommending anything
takt time = available production time / customer demand (units)
required capacity = forecast demand × cycle time per unit / (OEE × available hours)
OEE = availability × performance × quality (world-class ≈ 85%, typical 60% — rule of thumb)
availability = run time / planned production time (unplanned downtime lives here)
lead time = order received → order shipped (measure the whole chain, not one step)
utilization = scheduled load / demonstrated capacity (plan ≤ ~85%; 100% planning guarantees lateness)
Capacity planning (quarter/period level)
- Start from the demand forecast with its uncertainty, not the point estimate — plan the base case and a ±20% band (or the forecaster's stated range).
- Convert to required hours per work center using demonstrated (measured) cycle times and demonstrated OEE — never nameplate/vendor figures.
- Compare against available hours after subtracting planned maintenance, holidays, training, and changeovers. The gap is the decision: overtime, extra shift, outsourcing, or demand shaping.
- State the constraint explicitly (which work center is the bottleneck at base and high case); capacity added anywhere else is spend without output.
Preventive maintenance (PM) scheduling
- Classify equipment by criticality: bottleneck/single-point-of-failure machines get time-or-usage-based PM; redundant, cheap-to-fail assets can run to failure deliberately.
- PM interval: start from manufacturer guidance, then adjust on failure history (shorten after repeated unplanned failures, lengthen only with evidence).
- Schedule PM into the capacity plan (it consumes available hours); PM done "when we have time" is PM not done — that is how unplanned downtime returns.
- Track: unplanned downtime hours by machine and cause, MTBF, MTTR, PM compliance % (completed on schedule / scheduled). A PM program with <90% compliance is a paper program.
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.
- 11d ago First seen · 81 lines · 92 tokens per session scan A ee3b26f6f05b
manufacturing-ops-planning is a skill published in the GitHub repository anhnguyen0905/codex-mcp (3 stars, last pushed yesterday), licensed MIT. It adds 92 tokens to every session and 1,108 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-31.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…