Borrowing it
Nothing to install: this file belongs to DGouron/review-flow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DGouron/review-flow/master/.claude/skills/event-storming/SKILL.mdgit clone --depth 1 https://github.com/DGouron/review-flowWrote 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.
[](https://agentmods.dev/skills/dgouron/review-flow/event-storming)<a href="https://agentmods.dev/skills/dgouron/review-flow/event-storming"><img src="https://agentmods.dev/badge/skills/dgouron/review-flow/event-storming/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.
<a href="https://agentmods.dev/skills/dgouron/review-flow/event-storming"><img src="https://agentmods.dev/badge/skills/dgouron/review-flow/event-storming.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00064 | $0.02303 |
| Opus 5.5 | $0.00026 | $0.00921 |
| Sonnet 5.5 | $0.00013 | $0.00461 |
| Haiku 4.5 | $0.00006 | $0.00230 |
Grade C, and why
event-storming scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
cd /tmp && rm -rf review-flow.wiki How it starts
The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Event Storming Big Picture
Tu es un facilitateur Event Storming (Alberto Brandolini) specialise en DDD strategique pour ReviewFlow (Node.js, Fastify 5, Clean Architecture).
Tu appliques les patterns strategiques de Vaughn Vernon (Implementing Domain-Driven Design) pour le Context Mapping.
Terminologie Clean Architecture
Ce projet utilise la terminologie Clean Architecture, PAS DDD tactique.
| Clean Architecture (ce projet) | DDD tactique (NE PAS utiliser) |
|---|---|
Entity (entities/) |
Aggregate, Domain Entity |
Use Case (usecases/) |
Application Service, Command Handler |
Gateway contract (entities/<domain>/<domain>.gateway.ts) |
Repository, Port |
Gateway impl (interface-adapters/gateways/) |
Adapter, Repository Impl |
Controller (interface-adapters/controllers/) |
Inbound Adapter |
Presenter (interface-adapters/presenters/) |
Read Model Projection |
View (interface-adapters/views/) |
UI Component |
Guard (*.guard.ts) |
Specification, Validator |
Dans les livrables Event Storming, mapper vers cette terminologie :
- 🟨 Entity (pas "Aggregate") —
entities/<domain>/ - 🟦 Use Case (pas "Command Handler") —
usecases/*.usecase.ts - 🟩 Presenter (pas "Read Model") —
interface-adapters/presenters/*.presenter.ts - ⬜ Gateway (pas "Repository") —
entities/*/*.gateway.ts+interface-adapters/gateways/*
Coding Standards
Lire .claude/rules/coding-standards.md AVANT de travailler.
Ubiquitous Language
Lire docs/reference/ubiquitous-language.md — c'est la source de verite pour les termes du domaine.
Modes d'execution
Mode cible (par defaut)
Input : /event-storming <bc-name> (ex: review, tracking, insight, job)
Output : docs/ddd/event-storming/<bc-name>.md + mise a jour du document global
Mode audit global
Input : /event-storming global
Output : docs/ddd/EVENT_STORMING_BIG_PICTURE.md avec tous les BCs
What ships with it
1 file 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.
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 · 200 lines · 64 tokens per session scan C 789020e1925b
event-storming is a skill published in the GitHub repository DGouron/review-flow (44 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 2,303 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
brooks-harness
Maintenance orchestrator for the brooks-lint plugin itself. Runs a sequential subagent pipeline — author → eval → QA → trigger-audit → release — to add or edit a skill, refresh the eval suite, keep the four manifests + all README translations + CHANGELOG + AGENTS/GEMINI in sync, audit trigger boundaries, and cut…
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
new-skill
Scaffold a new brooks-lint analysis skill so it passes npm run validate and npm run evals on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends…
brooks-audit
Architecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books. Triggers when: user asks to audit architecture, review folder/module structure, check for circular imports, understand how the codebase is organized…
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
brooks-debt
Tech debt assessment that identifies, classifies, and prioritizes maintainability problems — helping teams build a refactoring roadmap — drawing on twelve classic engineering books. Triggers when: user asks about tech debt, refactoring priorities, what to clean up first, or asks "why is this so hard to change?", "what…