apply-contagion-risk-mapping

apply-contagion-risk-mapping is a skill for Claude Code from jeffreytse/grimoire-core. It costs 48 tokens per session (3,410 once invoked), scanned A, original, MIT.

A method for mapping how failures can spread through nearby organizations, shared infrastructure, and connected dependencies. It looks beyond direct partnerships to find less obvious exposure.

In plain words
What is it for?
Use it to assess dependencies between organizations, suppliers, systems, partners, or other connected entities. It helps identify where a failure elsewhere could disrupt your work.
Why use it?
Risk reviews that consider only direct relationships can miss how another organization's failure affects you indirectly. This helps reveal possible cascade paths before they become crises.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

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

Good fit Use it to assess dependencies between organizations, suppliers, systems, partners, or other connected entities. It helps identify where a failure elsewhere could disrupt your work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeffreytse/grimoire-core/apply-contagion-risk-mapping
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-contagion-risk-mapping
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 145 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-contagion-risk-mapping

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/apply-contagion-risk-mapping"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/apply-contagion-risk-mapping.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,410 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.00048 $0.03410
Opus 5 $0.00024 $0.01705
Sonnet 5 $0.00010 $0.00682
Haiku 4.5 $0.00005 $0.00341

Measured 9d ago against content hash 8e6fc9d4b701, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

apply-contagion-risk-mapping 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 9d 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-contagion-risk-mapping/SKILL.md · 101 lines

How it starts

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

Apply Contagion Risk Mapping

Map your exposure to cascade failures from entities in your implicit network — not just explicit strategic partners — because failure propagates through proximity and shared infrastructure, not only through deliberate relationships.

Why This Is Best Practice

左传 僖公五年 (655 BC) — 宫之奇谏假道:

虢,虞之表也。虢亡,虞必从之。唇亡则齿寒。

"Guo is the outer protection of Yu. If Guo falls, Yu must follow. When lips are gone, the teeth feel cold."

Why best: In 655 BC, the Duke of Jin requested passage through the state of Yu to attack the neighboring state of Guo. The minister Gong Zhiqi warned the Yu ruler against granting the passage: Yu and Guo were structurally interdependent — Guo provided outer protection to Yu without any formal alliance treaty requiring it. If Guo fell, Yu would be exposed and would inevitably follow. The Yu ruler granted the passage, Jin defeated Guo, and on the return march, Jin absorbed Yu as well. The classical commentators use this case as the canonical illustration of cascade failure through proximity: the threat did not come from a direct enemy relationship, but from the collapse of an adjacent entity that Yu had not recognized as load-bearing for its own survival. 唇亡齿寒 ("when lips are gone, the teeth feel cold") became standard vocabulary in Chinese strategic and risk analysis for implicit interdependence that only becomes visible when it fails.

Basel III Systemic Risk Framework (BIS, 2010): Enacted after the 2008 financial crisis, which demonstrated that individual firms can be solvent while the system collapses through contagion. Basel III introduced the concept of "systemically important financial institutions" (SIFIs) — entities whose failure creates cascade risk for others not directly connected to them contractually. The key finding: traditional risk models assessed bilateral exposure (what do I owe to, or own of, this counterparty?) but missed network-level exposure (what happens to me if an entity I depend on indirectly fails, or if shared funding sources dry up?). Basel III requires banks to hold additional capital buffers proportional to their systemic interconnectedness, not just their bilateral credit exposure. Standard across 28 BCBS member jurisdictions covering ~90% of global banking assets.

Read the full file on GitHub · 101 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. 9d ago First seen · 101 lines · 48 tokens per session scan A 8e6fc9d4b701

Subscribe to this mod's changes

apply-contagion-risk-mapping is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 24d ago), licensed MIT. It adds 48 tokens to every session and 3,410 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.