crisis-response

crisis-response is a skill for Claude Code from indranilbanerjee/digital-marketing-pro. It costs 28 tokens per session (679 once invoked), scanned A, original, MIT.

A structured plan for responding to a public-relations crisis. It assesses severity, identifies affected groups, drafts a holding statement, prepares audience-specific messages, and lays out an hour-by-hour communication timeline.

In plain words
What is it for?
Use it to assess what happened, decide who should be told and when, prepare an initial statement, assign a spokesperson, and plan longer-term trust rebuilding.
Why use it?
It turns an urgent, unclear incident into ordered communication steps and helps keep messages consistent across customers, employees, investors, partners, and the public. It drafts and plans only; it does not publish anything.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: reads .claude/ paths.

Part of the digital-marketing-pro plugin — 164 skills, 5 commands, 24 agents shipped together

Good fit Use it to assess what happened, decide who should be told and when, prepare an initial statement, assign a spokesperson, and plan longer-term trust rebuilding.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/indranilbanerjee/digital-marketing-pro/crisis-response
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 indranilbanerjee/digital-marketing-pro --skill crisis-response
Clone the repo
git clone --depth 1 https://github.com/indranilbanerjee/digital-marketing-pro

Made for: Claude Code.

Or install digital-marketing-pro, the plugin that ships this one along with the rest of its 164 skills, 5 commands, 24 agents.

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 crisis-response

README.md
[![agentmods](https://agentmods.dev/badge/skills/indranilbanerjee/digital-marketing-pro/crisis-response/github.svg)](https://agentmods.dev/skills/indranilbanerjee/digital-marketing-pro/crisis-response)
Your own site
<a href="https://agentmods.dev/skills/indranilbanerjee/digital-marketing-pro/crisis-response"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/digital-marketing-pro/crisis-response/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 crisis-response

Your own site · 80×15
<a href="https://agentmods.dev/skills/indranilbanerjee/digital-marketing-pro/crisis-response"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/digital-marketing-pro/crisis-response.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 679 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.00028 $0.00679
Opus 5.5 $0.00011 $0.00272
Sonnet 5.5 $0.00006 $0.00136
Haiku 4.5 $0.00003 $0.00068

Measured 4d ago against content hash 4048c734db16, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

crisis-response 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 4d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

skills/crisis-response/SKILL.md · 55 lines

How it starts

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

/digital-marketing-pro:crisis-response

Purpose

Provide rapid crisis assessment and a structured response plan. Classifies severity, identifies stakeholders, drafts messaging for each audience, and builds a communication timeline to contain damage and rebuild trust.

Input Required

The user must provide (or will be prompted for):

  • What happened: Description of the crisis or incident
  • When it started: Timeline of events so far
  • Current exposure: How widely known is it (internal only, social media, press coverage)
  • Stakeholders affected: Customers, employees, investors, partners, public
  • Actions taken so far: Any statements, fixes, or responses already issued
  • Spokesperson: Who will speak for the brand

Process

  1. Load brand context: Read ~/.claude-marketing/brands/_active-brand.json for the active slug, then load ~/.claude-marketing/brands/{slug}/profile.json. Apply brand voice, compliance rules for target markets (skills/context-engine/compliance-rules.md), and industry context. Also check for guidelines at ~/.claude-marketing/brands/{slug}/guidelines/_manifest.json — if present, load restrictions and relevant category files. Check for custom templates at ~/.claude-marketing/brands/{slug}/templates/. Check for agency SOPs at ~/.claude-marketing/sops/. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults.
  2. Severity classification: Level 1 (monitor), Level 2 (respond), Level 3 (full mobilization) based on reach, impact, and trajectory
  3. Assess the narrative: What is being said? What is the public sentiment? What is the worst-case escalation?
  4. Identify all stakeholder groups and prioritize communication order
  5. Draft holding statement for immediate release (within first hour)
  6. Draft tailored messaging per stakeholder: customers, employees, media, partners, social media
  7. Build communication timeline: first hour, first 24 hours, first week, ongoing
  8. Define channel strategy: which messages go where (social, email, press, internal comms)
  9. Outline recovery plan: corrective actions, transparency updates, trust-rebuilding initiatives
  10. Set monitoring cadence and escalation triggers

Read the full file on GitHub · 55 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. 4d ago Changed · -100 tokens per session 4048c734db16
  2. 1mo ago First seen · 55 lines · 128 tokens per session scan A 7072479743ea

Subscribe to this mod's changes

crisis-response is a skill published in the GitHub repository indranilbanerjee/digital-marketing-pro (882 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 679 once invoked, about $0.0001 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-07.