product-os: Command for Claude Code

.claude/commands/meeting-schedule.md

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

A meeting-scheduling command that finds a time shared by named attendees and creates the meeting while considering focus time and preferred meeting patterns.

In plain words
What is it for?
Use it to schedule meetings with one or more people by name, optionally giving a length and title.
Why use it?
It removes the back-and-forth of checking calendars and lets you specify the duration and title.

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-schedule.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-schedule

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/motorway-sandbox/product-os/meeting-schedule"><img src="https://agentmods.dev/badge/commands/motorway-sandbox/product-os/meeting-schedule.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,211 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.01211
Opus 5 $0.00000 $0.00606
Sonnet 5 $0.00000 $0.00242
Haiku 4.5 $0.00000 $0.00121

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

Security

Grade A, and why

meeting-schedule 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 7d 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-schedule.md · 119 lines

How it starts

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

Meeting Schedule

Find a mutually available time slot and schedule a meeting, respecting focus time and meeting clustering preferences.

Instructions

Step 0: Parse arguments

  • The user provides arguments in the format: $ARGUMENTS
  • Expected format: {name1}, {name2}, ... [| duration: {minutes}] [| title: {text}]
  • Pipe | separates the attendee names from optional parameters
  • Names: comma-separated list of people to meet with
  • duration: meeting length in minutes (default: 30)
  • title: meeting title (default: auto-generated from attendee names, e.g. "{YOUR_NAME} / Alex sync")
  • If no arguments are provided, use AskUserQuestion to ask who the meeting is with

Examples:

  • {PM 5} → 30 min meeting with Alex
  • Alex, Sam | duration: 60 → 60 min meeting with Alex and Sam
  • {CPO} | duration: 45 | title: Product strategy check-in → 45 min meeting with {CPO}

Step 1: Resolve names to email addresses

For each name provided, resolve to an email address using Slack:

  1. Use mcp__claude_ai_Slack__slack_search_users for each name — run all searches in parallel
  2. Handle results:
    • 1 match — use the email from their Slack profile
    • Multiple matches — present the options via AskUserQuestion and ask the user to pick
    • 0 matches — ask the user to provide the email address directly via AskUserQuestion

Collect all resolved email addresses before proceeding.

Step 2: Find candidate time slots

Use mcp__claude_ai_Google_Calendar__gcal_find_meeting_times with:

  • All attendee email addresses
  • startHour: 9
  • endHour: 17
  • maxResults: 15
  • Search window: next 5 working days (Monday–Friday)
  • Duration: as parsed from arguments (default 30 mins)

From the results, filter out any slots starting before 09:30.

If no slots are returned:

  1. Expand the search window to 10 working days
  2. If still no slots, inform the user and ask if they want to try a different duration or time range

Read the full file on GitHub · 119 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. 7d ago First seen · 119 lines · 0 tokens per session scan A 8c6f710d7daa

Subscribe to this mod's changes

meeting-schedule 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,211 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.