product-os: Command for Claude Code

.claude/commands/experiment-setup.md

experiment-setup is a command for Claude Code from motorway-sandbox/product-os. It costs 0 tokens per session (2,706 once invoked), scanned A, original, MIT.

An experiment-planning command that recommends how to set up a proposed product experiment. It looks at past experiments, suggests success measures, estimates sample size and duration, scores revenue potential, and writes experiment parameters.

In plain words
What is it for?
Use it when proposing an experiment, updating an experiment document, or stating a hypothesis in “If X, then Y, because Z” form. It can prepare the setup for a chosen part of a product funnel.
Why use it?
It helps turn an idea into a testable plan with defined measures and practical run estimates. An experiment here is a controlled test of a product change to see whether it improves a chosen result.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is motorway-sandbox/product-os's own configuration. It tells Claude Code how to work on product-os itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything product-os configures →

Reuse

Borrowing it

Nothing to install: this file belongs to motorway-sandbox/product-os. 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/motorway-sandbox/product-os/main/.claude/commands/experiment-setup.md
Clone the repo
git clone --depth 1 https://github.com/motorway-sandbox/product-os

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.

agentmods badge for experiment-setup

README.md
[![agentmods](https://agentmods.dev/badge/commands/motorway-sandbox/product-os/experiment-setup/github.svg)](https://agentmods.dev/commands/motorway-sandbox/product-os/experiment-setup)
Your own site
<a href="https://agentmods.dev/commands/motorway-sandbox/product-os/experiment-setup"><img src="https://agentmods.dev/badge/commands/motorway-sandbox/product-os/experiment-setup/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 experiment-setup

Your own site · 80×15
<a href="https://agentmods.dev/commands/motorway-sandbox/product-os/experiment-setup"><img src="https://agentmods.dev/badge/commands/motorway-sandbox/product-os/experiment-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,706 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.00000 $0.02706
Opus 5 $0.00000 $0.01353
Sonnet 5 $0.00000 $0.00541
Haiku 4.5 $0.00000 $0.00271

Measured 4d ago against content hash 6b5de65f0452, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

experiment-setup 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 4d 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/experiment-setup.md · 220 lines

How it starts

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

Experiment Setup

Generate a complete experiment setup recommendation for a proposed experiment. This command cross-references past experiments, estimates the right success metric, calculates sample size and run time, scores revenue potential (ROTI), and produces a ready-to-use experiment parameters section for the project doc.

Arguments

The user should provide one of:

  • A description of the proposed experiment (what they want to test and where)
  • A path to an existing project/experiment doc that needs setup parameters
  • A hypothesis in "If X, then Y, because Z" format

If insufficient context is provided, ask for: the intervention point (which funnel step), the hypothesised mechanism, and the engineering estimate (days).

Instructions

Phase 1: Past experiment lookup

Before calculating anything, search for similar past experiments to ground the analysis in evidence.

  1. Search the Notion Experimentation Tracker using mcp__claude_ai_Notion__notion-search against the data source {your-experiment-tracker-collection-id}. Search by:

    • Location of test — find experiments at the same funnel step (e.g. {your funnel steps, e.g. Sign-up page, Onboarding, Activation, Checkout})
    • Lever — find experiments using the same psychological/UX mechanism (e.g. Credibility, Effort, Trust, Urgency, User flow, Social Proof)
    • Pillar/Squad — find experiments from the same team area
  2. Fetch the top 3-5 most relevant completed experiments using mcp__claude_ai_Notion__notion-fetch and read their content for detailed metrics (funnel uplift, ARR impact, learnings).

  3. Search Hex using mcp__claude_ai_Hex__search_projects for experiment result dashboards with detailed analysis.

  4. Check local experiment docs in projects/ for full writeups with statistical analysis.

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

  1. 4d ago First seen · 220 lines · 0 tokens per session scan A 6b5de65f0452

Subscribe to this mod's changes

experiment-setup is a command published in the GitHub repository motorway-sandbox/product-os (9 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,706 tokens. 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-04.