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/daily-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/daily-prep)<a href="https://agentmods.dev/commands/motorway-sandbox/product-os/daily-prep"><img src="https://agentmods.dev/badge/commands/motorway-sandbox/product-os/daily-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/daily-prep"><img src="https://agentmods.dev/badge/commands/motorway-sandbox/product-os/daily-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.03315 |
| Opus 5 | $0.00000 | $0.01657 |
| Sonnet 5 | $0.00000 | $0.00663 |
| Haiku 4.5 | $0.00000 | $0.00331 |
Grade A, and why
daily-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 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.
How it starts
The opening of the file, as written. The whole thing — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daily Prep
Prep me for the day: review my calendar, prioritise my todo list, find focus time for high-priority work, and prep for each meeting. Save the output and deliver it to Telegram and Slack.
Instructions
Step 0: Identify the user
- Check auto-memory (MEMORY.md) for the user's initials, name, direct reports, and manager
- Set
{initials}accordingly (e.g.CR)
Step 1: Gather inputs (parallelise all of these)
-
Todo list — Read
team/{initials}/todo_list.md- Extract ALL open (not done) items from the main table
- Note priority (H/M/L), due date, and whether overdue
- Also extract "Waiting on Others" items
-
Calendar — Use
mcp__claude_ai_Google_Calendar__gcal_list_eventsto get all events for today- Set
condenseEventDetails: false— you need the full attendee list to filter by meeting size - If Calendar MCP is unavailable, fall back to reading 1:1 context files for known recurring meetings
- Set
-
Current priorities — Read
context/current-priorities.mdfor squad RAG statuses and initiative updates -
Agent state files — Read the following files if they exist (skip silently if missing):
team/{initials}/agents/cos.md— extract overdue follow-ups (Active items with status "chasing" where follow-up date is past by >3 working days), extract watch list items relevant to today or this weekteam/{initials}/agents/analyst.md— extract Active items (metric anomalies being watched), Segment health flags, any Experiments concluding this weekteam/{initials}/agents/uxr.md— extract Active items (converging themes), any signals relevant to today's meetingsteam/{initials}/agents/coach.md— extract Development tracker ratings and trends, Review compliance (flag any overdue reviews), Active items (operating themes)team/{initials}/agents/manager.md— extract PM tracker (per-PM three-pillar status), Active items (flags needing attention), any overdue Q1 reviews or Q2 goalsteam/{initials}/agents/strategist.md— extract Active items (open commitments to leadership), Exec feedback tracker, any approaching deadlinesteam/{initials}/agents/product-manager.md— extract Active investigations (what's being investigated and at what phase), Experiment pipeline (what's running), any blocked items or open threads- For each agent, note the "Last refreshed" timestamp — if stale (>48 hours on a working day), flag it in the brief
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.
- 7d ago First seen · 247 lines · 0 tokens per session scan A 5a55d8866cbd
daily-prep is a command published in the GitHub repository motorway-sandbox/product-os (10 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,315 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
standup
Quick daily standup from today's Claude Code sessions — grouped by project, with cost and errors.
fire-todos
Capture, list, and manage todos during work sessions.
gsd:resume-work
Resume work from previous session with full context restoration.
todo.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
standup
A command that creates a daily stand-up report by summarizing recent work, planned tasks, calendar events, and blockers.
ops
Weekly operations loop — triage the inquiry inbox, advance the CRM pipeline, sweep open PRs across repos, and surface the content plan. Loads the ops skill.