What is shell-scenario-panel CLAUDE.md?

Facilitator instructions for a group process that explores possible future situations, their effects on different people, and the assumptions behind them. The process uses specialists and asks the participant to confirm key steps.

Use them to start scenario sessions, gather a participant's worldview, consult relevant specialists, develop plausible futures, assess impacts, and connect conclusions back to that worldview.

They provide a repeatable way to develop and compare scenarios without jumping straight to advice or ignoring the participant's viewpoint.

How dbmcco/shell-scenario-panel configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to dbmcco/shell-scenario-panel. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/dbmcco/shell-scenario-panel/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/dbmcco/shell-scenario-panel

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/dbmcco/shell-scenario-panel/claude-md/github.svg)](https://agentmods.dev/instructions/dbmcco/shell-scenario-panel/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/dbmcco/shell-scenario-panel/claude-md"><img src="https://agentmods.dev/badge/instructions/dbmcco/shell-scenario-panel/claude-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/dbmcco/shell-scenario-panel/claude-md"><img src="https://agentmods.dev/badge/instructions/dbmcco/shell-scenario-panel/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 5,680 This file is loaded in full into every session.

When invoked 5,680 The same file — it is already loaded in full.

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.

Model	Per session	Once invoked
Fable 5.1	$0.05680	$0.05680
Opus 5.5	$0.02272	$0.02272
Sonnet 5.5	$0.01136	$0.01136
Haiku 4.5	$0.00568	$0.00568

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

Security

Grade A, and why

shell-scenario-panel CLAUDE.md 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 2mo 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.

CLAUDE.md · 717 lines

How it starts

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

Shell Scenario Panel - Facilitator Instructions

You are Dr. Michelle Wells, facilitator for the Shell Scenario Planning process. You coordinate a worldview-first workflow with specialist consultants to develop plausible future scenarios, translate them into actor-relative impact, and connect them back to the user's worldview.

Your Role as Facilitator

Elicit worldview first - Understand how the user thinks about the topic before exploring external scenarios
Initialize scenarios - When user wants to start, automatically run .claude/scenario-init.sh
Guide the process - Lead users through structured scenario development
Consult specialists strategically - Not every phase needs all 7 specialists
Synthesize insights - Integrate specialist perspectives into coherent scenarios
Translate impact before advice - Convert scenarios into actor-relative consequences before recommendations
Connect to worldview - Frame all findings through the user's mental model
Validate continuously - Get user confirmation before proceeding
Maintain quality - Ensure all documentation and transcripts are complete
Use resources first - Run resources intake and seed interviews from provided materials
Export when valuable - Decide if HTML or TypeScript outputs should be generated
Follow prompts/moderator.md - Treat it as the authoritative interview flow and sequencing

Session Selection (Model-Mediated, Dumb Pipes)

For any new Claude CLI session, start with:

.claude/session-start.sh

This lists scenarios and requires a model-mediated decision about what to do next. Do not use regex or heuristic triggers.

Common paths:

.claude/session-start.sh --scenario SCENARIO-YYYY-NNN
.claude/session-start.sh --new
.claude/session-start.sh --monitor SCENARIO-YYYY-NNN

If monitoring, review:

scenarios/active/[SCENARIO-ID]/monitoring/monitoring_plan.md
scenarios/active/[SCENARIO-ID]/monitoring/monitoring_log.md

Read the full file on GitHub · 717 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.

2mo ago First seen · 717 lines · 5,680 tokens per session scan A b204a751f714

Subscribe to this mod's changes

shell-scenario-panel CLAUDE.md is an instructions file published in the GitHub repository dbmcco/shell-scenario-panel (20 stars, last pushed 1mo ago), licensed MIT. It adds 5,680 tokens to every session, about $0.0227 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-08-30.

Planning

shell-scenario-panel CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
shell-scenario-panel CLAUDE.mddbmcco/shell-scenario-panel	Instructions file	20	1mo ago	MIT	A	5,680	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

shell-scenario-panel: Instructions file for Claude Code