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-schedule.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-schedule)<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.
<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>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.01211 |
| Opus 5.5 | $0.00000 | $0.00484 |
| Sonnet 5.5 | $0.00000 | $0.00242 |
| Haiku 4.5 | $0.00000 | $0.00121 |
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 2mo 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 — 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
AskUserQuestionto ask who the meeting is with
Examples:
{PM 5}→ 30 min meeting with AlexAlex, 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:
- Use
mcp__claude_ai_Slack__slack_search_usersfor each name — run all searches in parallel - Handle results:
- 1 match — use the email from their Slack profile
- Multiple matches — present the options via
AskUserQuestionand 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: 9endHour: 17maxResults: 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:
- Expand the search window to 10 working days
- If still no slots, inform the user and ask if they want to try a different duration or time range
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.
- 2mo ago First seen · 119 lines · 0 tokens per session scan A 8c6f710d7daa
meeting-schedule is a command published in the GitHub repository motorway-sandbox/product-os (11 stars, last pushed 5mo 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.
meeting-schedule compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| meeting-schedulemotorway-sandbox/product-os | Command | 11 | 5mo ago | MIT | A | 0 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |