A morning briefing command that gathers today’s calendar, important tasks, urgent messages, and upcoming deadlines.

Use it to review calendar events, overdue and upcoming tasks, urgent messages, meeting conflicts, back-to-back meetings, and meetings that need preparation.

Starting work by checking several separate tools can make it easy to miss conflicts or overdue work. The briefing puts the day’s priorities and time-sensitive items together.

gm — Command for Claude Code by mimurchison/claude-chief-of-staff

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/mimurchison/claude-chief-of-staff

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/mimurchison/claude-chief-of-staff/gm/github.svg)](https://agentmods.dev/commands/mimurchison/claude-chief-of-staff/gm)

Your own site

<a href="https://agentmods.dev/commands/mimurchison/claude-chief-of-staff/gm"><img src="https://agentmods.dev/badge/commands/mimurchison/claude-chief-of-staff/gm/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/mimurchison/claude-chief-of-staff/gm"><img src="https://agentmods.dev/badge/commands/mimurchison/claude-chief-of-staff/gm.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 684 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00684
Opus 5.5	$0.00000	$0.00274
Sonnet 5.5	$0.00000	$0.00137
Haiku 4.5	$0.00000	$0.00068

Measured 1mo ago against content hash ed559e8ce41d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

gm 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 1mo 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.

commands/gm.md · 95 lines

How it starts

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

/gm — Morning Briefing

Description

Start your day with a structured briefing: today's calendar, priority tasks, urgent messages, and upcoming deadlines. Know exactly what matters before you open your inbox.

Instructions

You are running the morning briefing for {{YOUR_NAME}}. Follow these steps in order, collecting information before presenting the final briefing.

Step 0: Get Current Time

Call the Google Calendar get-current-time tool to get the authoritative date and time. Extract the day of week, date, and timezone. Never guess the day of week — always verify.

Step 1: Calendar Review

Fetch today's calendar events using list-events with today's date range.

For each event, note:

Time and duration
Title and attendees
Whether it requires preparation
Any conflicts or back-to-back meetings

Flag:

Meetings that conflict with hard constraints (e.g., dinner time)
Back-to-back meetings with no buffer
Meetings with no clear agenda or purpose

Step 2: Task Review

Read ~/.claude/my-tasks.yaml and identify:

Tasks due TODAY (urgent)
Tasks OVERDUE (critical — should have been done)
Tasks due in the next 3 days (approaching)
Tasks that can be completed today given the calendar

Step 3: Goals Check

Read ~/.claude/goals.yaml and briefly assess:

Which goals have stalled (no progress update in 7+ days)?
Does today's calendar align with the highest-priority goals?
Any goal-aligned work that should be scheduled today?

Step 4: Inbox Quick Scan (if email MCP is connected)

Do a quick scan of email for anything urgent:

Search for emails from the last 12 hours
Flag Tier 1 items (from key contacts, marked urgent, or time-sensitive)
Don't do a full triage — just surface what's critical

Step 5: Present the Briefing

Format the briefing as follows:

Good morning. It's [Day], [Date]. Here's your day:

CALENDAR ([count] meetings)
- [time]  [title] ([duration]) [any flags]
- ...

[If applicable: "Heads up: [conflict or concern]"]

TASKS
- DUE TODAY: [list or "Nothing due today"]
- OVERDUE: [list or "All clear"]
- APPROACHING: [list of next 3 days]

GOALS
- [Brief status on top 1-2 goals, especially if stalled]

URGENT
- [Any Tier 1 items from inbox, or "No urgent items"]

FOCUS RECOMMENDATION
Based on your calendar and priorities, here's what I'd focus on today:
1. [Top priority]
2. [Second priority]
3. [Third priority, if time allows]

Read the full file on GitHub · 95 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.

1mo ago First seen · 95 lines · 0 tokens per session scan A ed559e8ce41d

Subscribe to this mod's changes

gm is a command published in the GitHub repository mimurchison/claude-chief-of-staff (461 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 684 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-08-30.

Productivity

ws

Word summary — anything told at N levels, from N words down to 1 word, for anything: a topic ("russian literature"), a URL, YouTube link, file, pasted text, a question, or "this". A leading number sets N (5 by default). Shortcut for the Fabric skill's WordSummary intent.

danielmiessler/LifeOS · 69 tokens

gm