design-crisis-management-governance-protocol

design-crisis-management-governance-protocol is a skill for Claude Code from jeffreytse/grimoire-core. It costs 82 tokens per session (1,404 once invoked), scanned A, original, MIT.

A governance plan for major corporate crises, such as a product safety failure, executive scandal, data breach, or disaster. It defines who can make decisions at each severity level and when the board must get involved.

In plain words
What is it for?
Creating a crisis chain of command, setting severity levels, and defining when operational leaders must involve the board.
Why use it?
Without agreed authority, teams can lose critical time deciding who may approve public statements, suspend executives, or notify regulators.

Skill for Claude Code

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

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

Good fit Creating a crisis chain of command, setting severity levels, and defining when operational leaders must involve the board.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeffreytse/grimoire-core/design-crisis-management-governance-protocol
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 design-crisis-management-governance-protocol
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 design-crisis-management-governance-protocol

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/design-crisis-management-governance-protocol"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/design-crisis-management-governance-protocol.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 82 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,404 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.00082 $0.01404
Opus 5.5 $0.00033 $0.00562
Sonnet 5.5 $0.00016 $0.00281
Haiku 4.5 $0.00008 $0.00140

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

Security

Grade A, and why

design-crisis-management-governance-protocol 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/operations/skills/design-crisis-management-governance-protocol/SKILL.md · 68 lines

How it starts

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

Design Crisis Management Governance Protocol

Establish a defined governance chain of command for a major corporate crisis — who has decision authority at each severity level, and specifically when the board itself must be activated — rather than discovering the chain of command for the first time while the crisis is already unfolding.

Why This Is Best Practice

Adopted by: The National Association of Corporate Directors documents defined crisis governance protocols — distinct from operational incident response — as a specific board oversight responsibility, since major corporate crises (executive misconduct, product safety failures, significant data breaches) frequently require board-level engagement beyond what a purely operational incident-response team can provide, particularly when the crisis involves the CEO or implicates the board's own oversight. Impact: Organizations without a pre-defined crisis governance protocol are documented to experience materially slower and more confused initial crisis response — precious early hours are spent determining who has authority to make key decisions (public statement approval, executive suspension, regulator notification) rather than executing an already-understood chain of command, a delay that compounds reputational and legal exposure during exactly the window when rapid, coordinated response matters most. Why best: A crisis is specifically the wrong moment to be determining governance structure for the first time — the pressure, time constraints, and stakes of an actual crisis are exactly the conditions under which an undefined chain of command produces the most costly delay and confusion, while a protocol established and understood in advance allows the organization to move directly to substantive crisis response rather than first resolving who's actually in charge.

Sources: National Association of Corporate Directors (NACD), crisis governance and board oversight guidance

Steps

Step 1: Define crisis severity tiers and the corresponding decision authority

Read the full file on GitHub · 68 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 · 68 lines · 82 tokens per session scan A a3e31ebdd36a

Subscribe to this mod's changes

design-crisis-management-governance-protocol is a skill published in the GitHub repository jeffreytse/grimoire-core (5 stars, last pushed 5d ago), licensed MIT. It adds 82 tokens to every session and 1,404 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.