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-crisis-opportunismgit 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-crisis-opportunism)<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/apply-crisis-opportunism"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/apply-crisis-opportunism/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-crisis-opportunism"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/apply-crisis-opportunism.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.00046 | $0.02147 |
| Opus 5 | $0.00023 | $0.01073 |
| Sonnet 5 | $0.00009 | $0.00429 |
| Haiku 4.5 | $0.00005 | $0.00215 |
Grade A, and why
apply-crisis-opportunism 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.
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apply Crisis Opportunism
Pre-position capability before a competitor's crisis hits, then move fast into undefended territory when the crisis diverts their attention and resources.
Why This Is Best Practice
Origin: Stratagem #5 of the Thirty-Six Stratagems: "Loot a burning house" (趁火打劫). When your opponent is fighting a fire inside their own walls, their defenders have moved to fight the fire — the walls themselves are unguarded. The stratagem's logic is not to cause the fire (that is a different stratagem) but to recognise it early, pre-position outside the walls, and move the moment the defenders are occupied elsewhere.
Adopted by: Crisis opportunism is one of the most consistently observed patterns in competitive history. Microsoft signed key software developers during IBM's PC strategy confusion in the early 1980s. Amazon accelerated AWS feature releases during competitors' cloud outages, building customer trust when alternatives were most visible. Enterprise software vendors routinely approach competitor customers at contract renewal — a moment of maximum openness — especially after a product failure, data breach, or executive departure. The pattern is not predatory by default; the crisis reveals which alternatives customers would have chosen anyway.
Impact: A competitor in crisis is not merely distracted — they are resource-constrained. Key people who would have defended key accounts are fighting the crisis. Sales teams are managing existing customers rather than closing new ones. Marketing is in crisis communications mode. The competitive positions they normally defend actively are, temporarily, passively held. Crisis windows are typically 90–180 days before effective triage and reallocation occurs.
Why best: Crisis opportunism is not about causing harm — it is about having built the capability to serve customers or capture positions that the opponent cannot currently defend. The ethical version: provide genuine alternatives that customers need, at a moment when they need them most. The pre-positioning requirement ensures the capability is real, not exploitative.
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 · 114 lines · 46 tokens per session scan A c14f3c3670a7
apply-crisis-opportunism is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 23d ago), licensed MIT. It adds 46 tokens to every session and 2,147 once invoked, about $0.0002 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
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.
infrastructure-as-code
Domain: DevOps & Cloud Engineering.
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.
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.