calendar

A read-only calendar command that views and analyzes events through icalBuddy, a Mac tool that reads calendars synced to the Apple Calendar app. It can work with calendars connected to services such as Google Calendar or iCloud.

In plain words
What is it for?
It is for listing and analyzing calendar events on macOS, checking available calendars, and diagnosing missing access or setup.
Why use it?
It lets an agent inspect scheduled events without changing them, while making the Mac-only setup and permission requirements clear.

Command for Claude Code

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.

agentmods
npx agentmods add commands/derek-larson14/delegate/calendar
Clone the repo
git clone --depth 1 https://github.com/derek-larson14/delegate

Made for: Claude Code.

Per session 13 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,264 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00013 $0.01264
Opus 5 $0.00006 $0.00632
Sonnet 5 $0.00003 $0.00253
Haiku 4.5 $0.00001 $0.00126

Measured 2d ago against content hash 91c9cabfe343, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

calendar 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 2d 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/calendar.md · 155 lines

How it starts

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

Calendar Assistant

Access calendar data via icalBuddy (reads from Mac Calendar app, which syncs with Google Calendar, iCloud, etc).

Mac only. If the user is on Windows or Linux, tell them: "/calendar uses a Mac-only tool. For calendar access, try Rube which can connect to Google Calendar, Outlook, and other services."

Setup (handle automatically)

Step 1: Check if icalBuddy is installed

which icalBuddy

If not found:

  1. Check if Homebrew exists: which brew
  2. If brew exists → run brew install ical-buddy yourself
  3. If no brew → tell user: "icalBuddy needs Homebrew. In Finder, open your workspace folder and double-click SETUP.command - it'll install Homebrew and the tools you need. Follow the prompts in the terminal window, then try /calendar again."

Step 2: Test calendar access

After installing (or if already installed), run:

icalBuddy calendars

If you see "error: No calendars." this means the app running Claude needs calendar permission. Tell the user:

Calendar permission needed. Go to System Settings → Privacy & Security → Calendars and enable:

  • Obsidian (if you're running Claude from Obsidian)
  • Terminal (if you're running Claude from Terminal)

If permission is already enabled but it's still not working, the permission entry might be corrupted. Run this in Terminal to reset Obsidian's calendar permission:

tccutil reset Calendar md.obsidian

Then try /calendar again and click Allow when macOS prompts.

If it lists calendars, you're good to proceed with their question.

Event Commands

# Today's events
icalBuddy eventsToday

# What's happening right now
icalBuddy eventsNow

# Today + N days (e.g., next 7 days)
icalBuddy eventsToday+7

# Specific date range (MUST use YYYY-MM-DD format, not relative words like 'tomorrow')
icalBuddy eventsFrom:'2025-01-20' to:'2025-01-25'

# Only events from now on (skip past events today)
icalBuddy -n eventsToday

# List all calendars
icalBuddy calendars

Read the full file on GitHub · 155 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. 2d ago First seen · 155 lines · 13 tokens per session scan A 91c9cabfe343

Subscribe to this mod's changes

calendar is a command published in the GitHub repository derek-larson14/delegate (39 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 1,264 once invoked, about $0.0001 per session on Opus 5. 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.