scenario-plan

scenario-plan is a command for Claude Code from abinauv/business-consulting. It costs 9 tokens per session (474 once invoked), scanned A, original, MIT.

A strategic-planning command that builds four possible futures from the biggest uncertain factors affecting a decision. Scenario planning explores different combinations of uncertain events instead of relying on one forecast.

In plain words
What is it for?
Listing key uncertainties, creating a 2×2 scenario matrix, estimating probabilities, identifying warning signs, assessing business effects, and stress-testing a strategy.
Why use it?
It makes assumptions and risks visible when the future is unclear. Comparing several outcomes helps test whether a strategy can cope with different conditions.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the business-consulting plugin — 16 skills, 24 commands shipped together

Good fit Listing key uncertainties, creating a 2×2 scenario matrix, estimating probabilities, identifying warning signs, assessing business effects, and stress-testing a strategy.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/abinauv/business-consulting/scenario-plan
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.

Clone the repo
git clone --depth 1 https://github.com/abinauv/business-consulting

Made for: Claude Code.

Or install business-consulting, the plugin that ships this one along with the rest of its 16 skills, 24 commands.

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 scenario-plan

README.md
[![agentmods](https://agentmods.dev/badge/commands/abinauv/business-consulting/scenario-plan/github.svg)](https://agentmods.dev/commands/abinauv/business-consulting/scenario-plan)
Your own site
<a href="https://agentmods.dev/commands/abinauv/business-consulting/scenario-plan"><img src="https://agentmods.dev/badge/commands/abinauv/business-consulting/scenario-plan/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 scenario-plan

Your own site · 80×15
<a href="https://agentmods.dev/commands/abinauv/business-consulting/scenario-plan"><img src="https://agentmods.dev/badge/commands/abinauv/business-consulting/scenario-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 474 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.00009 $0.00474
Opus 5 $0.00005 $0.00237
Sonnet 5 $0.00002 $0.00095
Haiku 4.5 $0.00001 $0.00047

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

Security

Grade A, and why

scenario-plan 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.

commands/scenario-plan.md · 50 lines

What it actually says

Scenario Planning

Develop strategic scenarios for $ARGUMENTS.

Instructions

1. Identify Key Uncertainties

  • List the 5-7 most impactful uncertainties affecting the strategic question
  • Rate each on two dimensions: Impact (H/M/L) and Uncertainty (H/M/L)
  • Select the top 2 uncertainties with highest impact AND highest uncertainty — these become your scenario axes

2. Build 2x2 Scenario Matrix

Use the two critical uncertainties as axes to create 4 distinct scenarios:

[Uncertainty 1: Outcome A] [Uncertainty 1: Outcome B]
[Uncertainty 2: Outcome A] Scenario 1: [Name] Scenario 2: [Name]
[Uncertainty 2: Outcome B] Scenario 3: [Name] Scenario 4: [Name]

Give each scenario a memorable, descriptive name.

3. Develop Each Scenario

For each of the 4 scenarios, describe:

  • Narrative: What does this world look like? (3-5 sentences)
  • Key indicators: What signals would tell us this scenario is materializing?
  • Impact on client: How does this scenario affect revenue, margins, competitive position?
  • Probability estimate: Likelihood of this scenario (all four should roughly sum to 100%)

4. Strategy Stress-Test

For the client's current strategy (or proposed strategy):

  • How does it perform in each scenario?
  • In which scenarios does it succeed? Fail?
  • What are the key vulnerabilities?

5. Robust Actions

Identify:

  • No-regret moves: Actions that create value in ALL scenarios
  • Options/hedges: Actions that preserve flexibility to pivot
  • Big bets: Actions that pay off hugely in one scenario but may fail in others

6. Monitoring Dashboard

  • For each scenario, define 3-5 leading indicators to watch
  • Define trigger points: "If [indicator] reaches [threshold], activate [contingency plan]"
  • Review frequency recommendation
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 · 50 lines · 9 tokens per session scan A 110c2d74e853

Subscribe to this mod's changes

scenario-plan is a command published in the GitHub repository abinauv/business-consulting (28 stars, last pushed 6mo ago), licensed MIT. It adds 9 tokens to every session and 474 once invoked, about $0.0000 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-08-30.

Related

Other commands, from other repositories

diagnose-underperformer

Diagnose why a specific Google Ads or Meta Ads campaign / ad set / ad is underperforming and prescribe the next concrete action. Use when the user says something like "why is X not converting?", "this campaign is wasting money", or "why are impressions so low?". Read-only — no changes are made.

markifact/markifact-mcp · 64 tokens

edit-meta-creative

Edit a Meta ad's creative content — landing page URL, primary text, headline, description, CTA, link description — across one ad or many. Use when the user says "change the URL on my ads", "update the copy", "swap the CTA", or anything that changes what an existing Meta ad shows. Meta does not allow in-place creative…

markifact/markifact-mcp · 88 tokens

rotate-creative

Pause fatigued ads and ship fresh creative variants in their place. Works on both Meta and Google Ads. Use when CTR is dropping, frequency is climbing, or the user says "creative is tired" / "let's refresh ads". Always starts new variants paused.

markifact/markifact-mcp · 53 tokens

launch-google-search

Launch a complete Google Ads Search campaign — campaign, ad group, responsive search ads, keywords, sitelinks, callouts, and negatives — built paused and ready to review. Use when the user wants to spin up a new Search campaign on Google Ads.

markifact/markifact-mcp · 52 tokens

launch-meta-campaign

Launch a complete Meta Ads campaign — campaign, ad set, and ad(s) — built paused and ready to review. Use when the user wants a new Facebook/Instagram campaign.

markifact/markifact-mcp · 36 tokens

launch-pmax

Launch a Google Ads Performance Max campaign with a complete asset group, audience signals, and (for ecom) listing groups. Built paused for review. Use when the user wants a new PMax campaign.

markifact/markifact-mcp · 41 tokens