apply-binding-constraint-removal

apply-binding-constraint-removal is a skill for Claude Code from jeffreytse/grimoire-core. It costs 67 tokens per session (4,032 once invoked), scanned A, original, MIT.

A strategy for finding the single operational limit that blocks a goal, confirming it is the real bottleneck, and solving it as an engineering or capability problem.

In plain words
What is it for?
Use it to diagnose supply, production, delivery, staffing, or technical bottlenecks and decide where to invest effort.
Why use it?
It helps avoid endlessly optimising around a constraint that may be removable and may be limiting everyone in the field.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: positional $N argument.

Part of the grimoire-business plugin — 156 skills shipped together

Good fit Use it to diagnose supply, production, delivery, staffing, or technical bottlenecks and decide where to invest effort.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeffreytse/grimoire-core/apply-binding-constraint-removal
Install

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.

Any agent
npx skills add jeffreytse/grimoire-core --skill apply-binding-constraint-removal
Clone the repo
git clone --depth 1 https://github.com/jeffreytse/grimoire-core

Made for: Claude Code.

Or install grimoire-business, the plugin that ships this one along with the rest of its 156 skills.

Wrote 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.

agentmods badge for apply-binding-constraint-removal

README.md
[![agentmods](https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/apply-binding-constraint-removal/github.svg)](https://agentmods.dev/skills/jeffreytse/grimoire-core/apply-binding-constraint-removal)
Your own site
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/apply-binding-constraint-removal"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/apply-binding-constraint-removal/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.

agentmods 80×15 button for apply-binding-constraint-removal

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/apply-binding-constraint-removal"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/apply-binding-constraint-removal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,032 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00067 $0.04032
Opus 5.5 $0.00027 $0.01613
Sonnet 5.5 $0.00013 $0.00806
Haiku 4.5 $0.00007 $0.00403

Measured 1mo ago against content hash 11b30b13a211, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

apply-binding-constraint-removal 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.

skills/business/strategy/skills/apply-binding-constraint-removal/SKILL.md · 128 lines

How it starts

The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Apply Binding Constraint Removal

Identify the single operational limit that is currently preventing your strategic goal — verify it is actually the binding constraint and not a symptom of a deeper one — then invest to solve it as an engineering or capability problem, rather than optimising around it as every competitor does, gaining structural advantage that is durable because competitors have built their entire operation on the assumption the constraint is permanent.

Why This Is Best Practice

Origin: Zhuge Liang's five northern expeditions (228–234 AD) against Cao Wei were repeatedly frustrated by the same operational limit: supply logistics in the Qinling mountain range between Shu Han (Sichuan) and Wei territory. The mountain roads were too narrow, too steep, and too unreliable to sustain supply lines adequate for a prolonged campaign. Cao Wei's generals — particularly Sima Yi — recognised this and adopted a consistent counter-strategy: avoid decisive battle, fortify, and wait for Shu's supply lines to collapse, forcing Zhuge Liang to retreat. Rather than accepting this constraint as permanent — as every other commander in the same terrain had — Zhuge Liang invented solutions. The wooden ox (木牛) and gliding horse (流马) were mechanical transport systems: improved load-carrying devices for mountain terrain, typically identified by historians as refined single-wheel barrow variants optimised for the specific terrain of the Qinling roads. He also modified the repeating crossbow (连弩) to increase its rate of fire, allowing fewer soldiers to project more firepower — addressing a related constraint on force multiplier efficiency. Each invention directly targeted the operational constraint that was limiting the strategic objective. The supply breakthrough was not complete — the strategic goal of reunifying Han was ultimately not achieved — but the inventions extended Zhuge Liang's campaign capacity beyond what any predecessor in the same terrain had achieved.

Read the full file on GitHub · 128 lines

Changes

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.

  1. 1mo ago First seen · 128 lines · 67 tokens per session scan A 11b30b13a211

Subscribe to this mod's changes

apply-binding-constraint-removal is a skill published in the GitHub repository jeffreytse/grimoire-core (5 stars, last pushed 5d ago), licensed MIT. It adds 67 tokens to every session and 4,032 once invoked, about $0.0003 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.