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.
curl -O https://raw.githubusercontent.com/motorway-sandbox/product-os/main/.claude/commands/meeting-prep.mdgit clone --depth 1 https://github.com/motorway-sandbox/product-osWrote 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/commands/motorway-sandbox/product-os/meeting-prep)<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.
<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>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.00000 | $0.01848 |
| Opus 5 | $0.00000 | $0.00924 |
| Sonnet 5 | $0.00000 | $0.00370 |
| Haiku 4.5 | $0.00000 | $0.00185 |
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.
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:
- Use
mcp__claude_ai_Google_Calendar__gcal_list_eventsto get events in the next 24 hours - Filter to meetings that look like 1:1s or recurring syncs (exclude all-hands, large group meetings, focus time)
- Present the next 3 candidate meetings using
AskUserQuestionand ask the user to confirm which one to prep for
- Use
- 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.
-
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
-
Previous meeting notes (Granola) — Use
mcp__claude_ai_Granola__list_meetings(withlast_30_daysor 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_transcriptand 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
- Use
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.
- 6d ago First seen · 178 lines · 0 tokens per session scan A 2b6d73b05820
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.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.