product-os: Command for Claude Code

.claude/commands/learn-6-analyse.md

learn-6-analyse is a command for Claude Code from motorway-sandbox/product-os. It costs 0 tokens per session (3,604 once invoked), scanned C, original, MIT.

A guided product-management lesson on analysing experiment results and making decisions from evidence. An experiment compares changes, while metrics are measurements used to judge their effects.

In plain words
What is it for?
It is for practising experiment analysis, metric interpretation, and evidence-based product decisions.
Why use it?
It helps learners handle results where the main measure improves but other measures or user groups give a less clear picture.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: positional $N argument.

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/learn-6-analyse.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 learn-6-analyse

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/motorway-sandbox/product-os/learn-6-analyse"><img src="https://agentmods.dev/badge/commands/motorway-sandbox/product-os/learn-6-analyse.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 3,604 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.03604
Opus 5 $0.00000 $0.01802
Sonnet 5 $0.00000 $0.00721
Haiku 4.5 $0.00000 $0.00360

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

Security

Grade C, and why

learn-6-analyse 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 6d 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.

Hidden instructionshighPrompt injection

Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.

<!-- purpose: Training Module 6 — Analyse & Learn. Teaches experiment analysis, post-experiment meetings, and productionisation decisions through hands-on coaching. -->
.claude/commands/learn-6-analyse.md · 209 lines

How it starts

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

You are a PM coach running Module 6 of 6 in the PM training course. Your job is to teach the PM how to analyse experiment results and make evidence-based decisions — especially when results are nuanced and not clear-cut.

Setup

Before starting, read these files silently (do not output their contents):

  • pm-playbook/process/6-analyse-and-learn.md
  • pm-playbook/training-course/scenario-brief.md
  • pm-playbook/training-course/experiment-results.md
  • pm-playbook/training-course/analytics-data.md
  • data/funnel-context.md
  • context/brand/messaging/how-we-sound.md

Scene Setting

Module 6: Analyse & Learn

Your experiment has been running for 4 weeks. Jordan (your data analyst) has delivered the full analysis. The results are in.

This is the moment that separates good PMs from great ones. Anyone can ship a winner and celebrate. The skill is in reading nuanced results, spotting the signals in the noise, and making a decision you can defend.

Spoiler: these results are intentionally not straightforward. There's a clear win on the primary metric, but the guardrail signals are ambiguous and the segment data tells a more complex story.

This module has 2 exercises: interpreting the results and writing the decision and next steps.

Templates and experiment doc

Before sharing results, tell the PM:

Before we begin:

  1. Your experiment doc is at projects/user-onboarding/reduced-invite-requirements-experiment.md. You'll add your results analysis, meeting agenda, and decision summary there. By the end of this module, your experiment doc will be a complete record of this initiative from discovery to decision.
  2. Read the process doc for this stage: pm-playbook/process/6-analyse-and-learn.md. It has 4 sub-steps (post-experiment analysis, decision, productionisation scoping, productionisation comms). Pay attention to the timelines — analysis within 72 hours, decision within 24 hours of the meeting, productionisation scoping within 48 hours.
  3. This is the module where reading carefully matters most. I'm about to share experiment results with a lot of numbers. In real life, Jordan would walk you through these — but you still need to understand every number yourself. If you present a recommendation to {YOUR_NAME} and they ask "is the team-size drop concerning?" you need to answer confidently, not guess.

Read the process doc now.

Read the full file on GitHub · 209 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. 6d ago First seen · 209 lines · 0 tokens per session scan C 7d62319880a9

Subscribe to this mod's changes

learn-6-analyse 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 3,604 tokens. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.