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 jeffreytse/grimoire-core --skill apply-theory-of-constraintsgit clone --depth 1 https://github.com/jeffreytse/grimoire-coreWrote 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/jeffreytse/grimoire-core/apply-theory-of-constraints)<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/apply-theory-of-constraints"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/apply-theory-of-constraints/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/jeffreytse/grimoire-core/apply-theory-of-constraints"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/apply-theory-of-constraints.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.00051 | $0.01729 |
| Opus 5.5 | $0.00020 | $0.00692 |
| Sonnet 5.5 | $0.00010 | $0.00346 |
| Haiku 4.5 | $0.00005 | $0.00173 |
Grade A, and why
apply-theory-of-constraints 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 1mo 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apply Theory of Constraints
Find the single resource that caps a system's throughput, subordinate everything else to it, then elevate it — instead of optimizing parts of the system that aren't the limiting factor.
Why This Is Best Practice
Adopted by: APICS/ASCM (constraint management is a core body-of-knowledge domain in CPIM certification), manufacturers worldwide via Drum-Buffer-Rope scheduling (Ford, Boeing suppliers, Amazon fulfillment network design documented case studies), the Theory of Constraints Institute's certified practitioner network, and widely taught in MBA operations curricula alongside Lean and Six Sigma. Impact: Goldratt Institute case-study compilations and independent TOC literature reviews (Mabin & Balderstone, 2003, "The performance of the theory of constraints methodology," meta-analysis of ~80 published TOC implementations) report median lead-time reductions of ~70%, inventory reductions of ~49%, and revenue/throughput increases of ~63% across manufacturing and project environments. Individual documented cases (e.g., GM's Powertrain Division, Boeing) report double-digit throughput gains within a single fiscal year of implementing the Five Focusing Steps. Why best: Most process-improvement effort defaults to optimizing whatever is easiest to see or measure — busy workers, idle machines, backlog size at any one step. TOC's core insight is that a chain's strength is set by its weakest link: improving any non-constraint resource does not increase system throughput and often just moves inventory or wait time to the real bottleneck. TOC forces improvement effort onto the one point that actually changes the system's output.
Sources: Goldratt & Cox, "The Goal" (1984); Goldratt, "It's Not Luck" (1994); Mabin & Balderstone (2003), International Journal of Operations & Production Management; APICS/ASCM CPIM Body of Knowledge
Steps
The Five Focusing Steps — run them in order, and treat step 5 as a loop back to step 1, not an end point.
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.
- 1mo ago First seen · 54 lines · 51 tokens per session scan A 93867f49ed8f
apply-theory-of-constraints is a skill published in the GitHub repository jeffreytse/grimoire-core (5 stars, last pushed 5d ago), licensed MIT. It adds 51 tokens to every session and 1,729 once invoked, about $0.0002 per session on Opus 5.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
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
deep-work-optimization
Focus blocks, distraction management, and flow state triggers for cognitively demanding work.
make-skill-template
Create new Agent Skills for GitHub Copilot from prompts or by duplicating this template. Use when asked to "create a skill", "make a new skill", "scaffold a skill", or when building specialized AI capabilities with bundled resources. Generates SKILL.md files with proper frontmatter, directory structure, and optional…
meeting-efficiency
Agenda design, time boxing, decision capture, async alternatives, and productive facilitation.
disagreement-protocol
Canonical phrasing for respectful disagreement without capitulation — structural resistance to sycophancy.
fix-once-auto-inject
One-time fixes get repeated manually.