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-competitive-patiencegit 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-competitive-patience)<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/apply-competitive-patience"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/apply-competitive-patience/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-competitive-patience"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/apply-competitive-patience.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.00049 | $0.02188 |
| Opus 5.5 | $0.00020 | $0.00875 |
| Sonnet 5.5 | $0.00010 | $0.00438 |
| Haiku 4.5 | $0.00005 | $0.00219 |
Grade A, and why
apply-competitive-patience 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apply Competitive Patience
Deliberately abstain from a competition that is exhausting your rivals, pre-position while they deplete each other, and enter after the battle has weakened the winner.
Why This Is Best Practice
Origin: Two stratagems from the Thirty-Six Stratagems address competitive patience from different angles. Stratagem #4 "Wait at ease for the enemy labored" (以逸待勞): preserve your resources while forcing opponents to exhaust theirs — let them come to you on ground you have prepared. Stratagem #9 "Watch the fires from the opposite bank" (隔岸觀火): when rivals are fighting each other, stay on the far bank and observe — intervene only when the fire has done the work for you. Both stratagems share the counter-intuitive insight that inaction at the right moment can be more decisive than action.
Adopted by: Competitive patience is the strategic logic behind the VHS/Betamax outcome (JVC maintained patience on format while Sony committed fully to Betamax; JVC built the OEM coalition that won), the browser wars (Google built web services while Microsoft and Netscape fought; when the dust settled, Google owned the web platform), and Toyota's position during the US auto industry's quality crisis of the 1980s (Toyota pre-positioned in reliability while the Big Three fought over market share). Kim & Mauborgne's Blue Ocean Strategy formalises one dimension of this: compete in uncontested space while rivals fight in the red ocean.
Impact: Direct entry into a market battle between committed rivals is expensive: you bear full market development cost while sharing the win with existing combatants. Competitive patience converts the rivals' investment in fighting each other into your market-entry advantage: the format war establishes the category, the price war educates customers, the standards fight reveals which architecture wins — all at no cost to you.
Why best: The hardest competitive discipline is doing nothing when action is available. Competitive patience requires an explicit decision — not drift, not resource constraints — to abstain from a battle that will exhaust rivals while you prepare. The decision to abstain must be backed by active pre-positioning; otherwise it is not strategy but avoidance.
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 · 110 lines · 49 tokens per session scan A 198203cfff28
apply-competitive-patience is a skill published in the GitHub repository jeffreytse/grimoire-core (5 stars, last pushed 5d ago), licensed MIT. It adds 49 tokens to every session and 2,188 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
semantic-model-disambiguation
Analyze Power BI semantic models for column-level overlaps that confuse Copilot and Fabric data agents. Detect ambiguity, review with domain expert, apply fixes via MCP.
prompt-2-data
Generate comprehensive synthetic relational data for any specified subject with multiple normalized CSV files maintaining referential integrity.
academic-paper-drafting
End-to-end academic paper drafting for CHI, HBR, journals, and conferences with venue-specific templates, drafting workflows, and revision strategies.
research-first-development
Build knowledge bases that build software — research before code, teach before execute.
infrastructure-as-code
Domain: DevOps & Cloud Engineering.
agent-governance
Patterns for adding safety, trust, and policy enforcement to AI agent systems -- control which tools agents can call, what content they process, and maintain accountability through audit trails.