A decision-simulation command that maps two or three possible paths from a specific choice, including dependencies, timing, and warning signs.

It helps model “what if” situations, compare decision branches, and define signals that would show whether a path is working.

It makes the consequences and contingencies of a decision easier to compare using information already stored in memory.

How marciopuga/cog configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to marciopuga/cog. 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/marciopuga/cog/main/.claude/commands/scenario.md

Clone the repo

git clone --depth 1 https://github.com/marciopuga/cog

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/commands/marciopuga/cog/scenario/github.svg)](https://agentmods.dev/commands/marciopuga/cog/scenario)

Your own site

<a href="https://agentmods.dev/commands/marciopuga/cog/scenario"><img src="https://agentmods.dev/badge/commands/marciopuga/cog/scenario/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/commands/marciopuga/cog/scenario"><img src="https://agentmods.dev/badge/commands/marciopuga/cog/scenario.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 47 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,919 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.

Model	Per session	Once invoked
Fable 5.1	$0.00047	$0.01919
Opus 5.5	$0.00019	$0.00768
Sonnet 5.5	$0.00009	$0.00384
Haiku 4.5	$0.00005	$0.00192

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

Security

Grade A, and why

scenario 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/commands/scenario.md · 205 lines

How it starts

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

Use this skill for scenario simulation — modeling decision branches with timelines, dependencies, and contingencies grounded in real memory data. Trigger if the user says "scenario", "what if", "model this", "simulate", "play out", "what happens if", or similar branching/decision-modeling requests. Also triggered when the foresight skill flags a scenario candidate in its nudge.

Memory Path

All files under the resolved memory path: $COG_HOME/memory/ if COG_HOME is set, otherwise ~/cog/memory/. All memory/... references below are relative to this root.

This is NOT foresight. Foresight = scan broadly, write one nudge. Scenario = take a specific decision point, branch it into 2-3 paths, map dependencies and timelines for each. Foresight finds the question. Scenario models the answers.

This is NOT reflect. Reflect = past-facing, mines interactions, improves memory. Scenario = future-facing, models possible futures from a decision point. Reflect checks old scenarios against reality (the feedback loop), but scenario creates them.

Domain

Cross-domain decision modeling — personal, work, projects, health, family. Scenarios are most valuable when a decision in one domain has cascading effects across others.

Memory Files

Read based on scenario topic — this is focused, not a broad scan:

memory/hot-memory.md (cross-domain strategic context)
memory/personal/calendar.md (upcoming timeline for overlay)
memory/personal/action-items.md (existing commitments, constraints)
Work domain action-items (read memory/domains.yml for active work domains)
Relevant domain hot-memory and entity files based on the scenario topic
memory/cog-meta/scenarios/ (existing scenarios — check for duplicates or related active scenarios; resolved ones carry a ## Retrospective worth reading before you predict again)

Process

1. Decision Point Identification

From user input or foresight seed, identify the specific decision point. A valid scenario requires:

A fork — at least 2 meaningfully different paths forward
Stakes — the outcome matters enough that choosing wrong has real cost (time, money, relationships, health)
Uncertainty — the right choice isn't obvious from current information
Time sensitivity — the decision window is closing or the consequences unfold on a timeline

Read the full file on GitHub · 205 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 Changed 254ebcceeca8
2mo ago First seen · 205 lines · 47 tokens per session scan A f3297eb60489

Subscribe to this mod's changes

scenario is a command published in the GitHub repository marciopuga/cog (377 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 1,919 once invoked, about $0.0002 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

scenario next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
scenariomarciopuga/cog	Command	377	2mo ago	MIT	A	47	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code

cog: Command for Claude Code