product-os: Command for Claude Code

.claude/commands/meeting-prep.md

meeting-prep is a command for Claude Code from motorway-sandbox/product-os. It costs 0 tokens per session (1,848 once invoked), scanned A, original, MIT.

A command that prepares a meeting brief from earlier meetings, open actions, quarterly goals, and one-to-one notes.

In plain words
What is it for?
It is for preparing one-to-one and small-group meetings, identifying the meeting, and summarizing relevant follow-up work.
Why use it?
It gathers scattered context so the user does not have to search through calendars and files before a meeting.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: names the AskUserQuestion tool.

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/meeting-prep.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 meeting-prep

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/motorway-sandbox/product-os/meeting-prep"><img src="https://agentmods.dev/badge/commands/motorway-sandbox/product-os/meeting-prep.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 1,848 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.01848
Opus 5 $0.00000 $0.00924
Sonnet 5 $0.00000 $0.00370
Haiku 4.5 $0.00000 $0.00185

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

Security

Grade A, and why

meeting-prep 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 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.

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/meeting-prep.md · 178 lines

How it starts

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

Meeting Prep

Generate a prep brief for an upcoming meeting by pulling context from previous meetings, open actions, quarterly goals, and the person's 1:1 context file.

Instructions

Step 0: Parse arguments and identify the meeting

  • The user provides arguments in the format: $ARGUMENTS
  • Expected format: {person name} (e.g. {CPO}, Alex, Product small group)
  • If no argument is provided:
    1. Use mcp__claude_ai_Google_Calendar__gcal_list_events to get events in the next 24 hours
    2. Filter to meetings that look like 1:1s or recurring syncs (exclude all-hands, large group meetings, focus time)
    3. Present the next 3 candidate meetings using AskUserQuestion and ask the user to confirm which one to prep for
  • Once the meeting is identified, determine:
    • Person name — the other attendee (for 1:1s) or the meeting name (for group meetings)
    • Slug — lowercase, hyphenated version (e.g. alex-smith, jane-doe)
  • Check the auto-memory (MEMORY.md) to identify the user's initials and their direct reports/manager
  • Classify the meeting type:
    • report — if the person is one of the user's direct reports
    • manager — if the person is the user's manager
    • other — any other meeting (peer, exec, group sync)

Step 1: Gather context (run in parallel)

Pull from all available sources. Run independent queries in parallel.

  1. Recurring meeting context file — Read team/{initials}/recurring-meeting-context/{slug}.md

    • If the file exists: extract standing topics, development themes, carry-forward items, and relationship notes
    • If the file does not exist: note this and proceed. After the brief is generated, offer to create one
  2. Previous meeting notes (Granola) — Use mcp__claude_ai_Granola__list_meetings (with last_30_days or a custom range) to find recent meetings, then filter by this person's name in the title or participants to identify the most recent 1-3 meetings

    • Use mcp__claude_ai_Granola__get_meetings (batch, up to 10 IDs) to retrieve notes and summaries
    • If notes are sparse (just a few words or empty), use mcp__claude_ai_Granola__get_meeting_transcript and extract key points
    • From the most recent meeting, extract:
      • Topics discussed
      • Decisions made
      • Open actions (especially anything assigned to the user or the other person)
      • Unresolved questions or threads

Read the full file on GitHub · 178 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 · 178 lines · 0 tokens per session scan A 2b6d73b05820

Subscribe to this mod's changes

meeting-prep 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 1,848 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.