simulation

simulation is a skill for Claude Code from melodic-software/claude-code-plugins. It costs 153 tokens per session (4,110 once invoked), scanned A, original, MIT.

An interactive workshop simulator for EventStorming, a collaborative method for mapping how a business or software domain works. It uses several simulated viewpoints to explore processes, groups of related responsibilities, and detailed designs, with optional Miro board support.

In plain words
What is it for?
It can simulate a full EventStorming workshop, explore a selected bounded context, or turn an existing process model into a detailed design.
Why use it?
It helps teams discover and discuss a complex domain before choosing system boundaries or designing software.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the event-storming plugin — 1 skill shipped together

Good fit It can simulate a full EventStorming workshop, explore a selected bounded context, or turn an existing process model into a detailed design.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add melodic-software/claude-code-plugins
Claude Code
/plugin install event-storming

Made for: Claude Code.

Or install event-storming, the plugin that ships this one along with the rest of its 1 skill.

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 simulation

README.md
[![agentmods](https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/simulation/github.svg)](https://agentmods.dev/skills/melodic-software/claude-code-plugins/simulation)
Your own site
<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/simulation"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/simulation/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 simulation

Your own site · 80×15
<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/simulation"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/simulation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 153 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,110 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.00153 $0.04110
Opus 5.5 $0.00061 $0.01644
Sonnet 5.5 $0.00031 $0.00822
Haiku 4.5 $0.00015 $0.00411

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

Security

Grade A, and why

simulation 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 3d ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/build-bc-view.mjs, scripts/build-bc-view.test.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

plugins/event-storming/skills/simulation/SKILL.md · 191 lines

How it starts

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

Arguments. <--simulate|--process-model|--design-level|--evaluate|--retrospective…> [domain|board]. Modes: --simulate|--process-model|--design-level|--evaluate|--retrospective|--induction|--value|--crc|--ux|--discover-bcs. Domain applies to --simulate, --retrospective, --induction, --ux; a board URL or bounded-context name applies to --process-model, --design-level; a board URL applies to --value, --crc, --discover-bcs; --evaluate takes none.

Variables

Arguments: $ARGUMENTS

Argument Parsing

Parse $ARGUMENTS for a simulation mode:

  • --simulate [domain]: Run a full simulation cycle with interactive progression. Loads agentic-simulation.md and simulation-evaluation.md. Starts with Big Picture, identifies bounded contexts, then uses AskUserQuestion to guide the user through selecting which BC to explore next. Domain defaults to "Developer Conference" if not specified. See "Running a Simulation" below.
  • --process-model [board-url-or-bc-name]: Run Process Modeling only, against an existing Big Picture board. Reads the BP board to extract the winning problem / selected BC, then executes PM with the 3-pass technique. Use when the user wants to deep-dive a specific BC without re-running Big Picture.
  • --design-level [board-url-or-bc-name]: Run Design-Level only, against an existing Process Modeling board. Reads the PM board to extract the process model, then executes DL with Blank Aggregates technique. Use when the user wants to go from PM → DL on a specific bounded context.
  • --evaluate: Run the iteration workflow against existing boards. Loads iteration-workflow.md and simulation-evaluation.md. Executes: SCORE → COMPARE → DIFF → FIX → VERIFY → CODIFY. Requires existing boards (reads the run-state store, ${CLAUDE_PLUGIN_DATA}/history.jsonl, for board URLs).
  • --retrospective [domain]: Run Big Picture as an organization retrospective, exploring an existing business process to find improvement opportunities. Frames exploration as "what ACTUALLY happens?" vs the official version. Same phases as --simulate but with a focus on problems/opportunities in existing flows rather than new product discovery. (Book Ch. 1 story 4, Ch. 10)
  • --induction [domain]: Run Big Picture as a new hire onboarding exercise. The New Hire persona leads (models based on guessing/assumptions), senior personas correct and explain. Implements Brandolini's "give newcomers the leading role" (Ch. 10). Produces a learning-oriented model, not a definitive one.
  • --value [board-url]: Run standalone Value Exploration against an existing Big Picture board. Executes all 5 sub-rounds: Financial value → Non-financial currencies → Contrasting perspectives → Diverging perspectives (customer segments) → Explore Purpose. (Book Ch. 5)
  • --crc [board-url]: Run Event-Driven CRC Cards validation against an existing Design-Level board. Assigns each aggregate to a separate agent, passes command/event cards between them with "tell don't ask" constraint. Validates interaction patterns work. (Book Ch. 22)
  • --ux [domain]: Run UX-Driven EventStorming, Process Modeling with a user journey focus. Follows the customer/user through the process, evaluating emotional experience, friction points, and "flawless execution" at each step. Uses standard PM color grammar plus emotional annotations. (Book preface + Brandolini's "Transactions Redefined" talk)
  • --discover-bcs [board-url]: Run Bounded Context discovery against an existing Big Picture board. Reads ALL board items via MCP, applies Brandolini's 6 heuristics (Ch. 6) mechanically against the data, and produces a structured BC analysis with heuristic evidence. Can be run at any time against any completed BP board. Results are reproducible. See "Bounded Context Discovery Protocol" below.

Read the full file on GitHub · 191 lines

Files

What ships with it

8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 3d ago Changed · -1 lines d7192e696e31
  2. 13d ago Changed · +11 lines 8e57b88bd755
  3. 16d ago Changed · +2 lines 7c5f1fc27e5b
  4. 22d ago Changed · +3 lines d303297a0b1b
  5. 1mo ago Changed · +6 lines c737040d7a30
  6. 1mo ago Changed 2cf104ffcc15
  7. 1mo ago First seen · 170 lines · 153 tokens per session scan A aa5ea50bab7f

Subscribe to this mod's changes

simulation is a skill published in the GitHub repository melodic-software/claude-code-plugins (25 stars, last pushed today), licensed MIT. It adds 153 tokens to every session and 4,110 once invoked, about $0.0006 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.

Related

Other skills, from other repositories

parallel-orchestrator

Manage parallel Claude Code workstreams using git worktrees. Use when: splitting large tasks across multiple workers, coordinating parallel development, monitoring worker progress, integrating completed work, analyzing work item documents (code reviews, issue lists). Triggers: parallel, orchestrator, worktrees…

jimmc414/claude-code-plugin-marketplace · 78 tokens

parallel-worker

Execute focused implementation tasks in a parallel workflow. Use when: working on assigned files in a worktree, making checkpoint commits, signaling dependencies or blockers, completing orchestrator-assigned tasks. Triggers: worker, checkpoint, worktree, assigned scope, commit prefix, parallel task.

jimmc414/claude-code-plugin-marketplace · 59 tokens

optimize-local-search

For NP-hard optimization: TSP, scheduling, assignment problems. Uses greedy construction + local improvement (2-opt, hill climbing).

jimmc414/claude-code-plugin-marketplace · 31 tokens

pass-function-as-arg

For generic algorithms: strategy pattern, callbacks, configurable behavior. Pass functions as parameters to customize algorithm behavior.

jimmc414/claude-code-plugin-marketplace · 27 tokens

solve-constraint-puzzle

For constraint satisfaction: Sudoku, scheduling, N-queens, logic puzzles, SAT-like problems, assignment problems. Uses propagate-then-search pattern.

jimmc414/claude-code-plugin-marketplace · 36 tokens

test-with-examples

For example-driven development: test cases as specifications, input/output pairs, documentation through examples.

jimmc414/claude-code-plugin-marketplace · 23 tokens