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.
npx agentmods add commands/omarshahine/apple-pim/calendarsgit clone --depth 1 https://github.com/omarshahine/apple-pimWrote 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/omarshahine/apple-pim/calendars)<a href="https://agentmods.dev/commands/omarshahine/apple-pim/calendars"><img src="https://agentmods.dev/badge/commands/omarshahine/apple-pim/calendars.svg" alt="Measured on agentmods" 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.00018 | $0.01453 |
| Opus 5 | $0.00009 | $0.00727 |
| Sonnet 5 | $0.00004 | $0.00291 |
| Haiku 4.5 | $0.00002 | $0.00145 |
Grade A, and why
calendars 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 5d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Calendar Management
Manage calendar events using the Apple EventKit framework.
Available Operations
When the user runs this command, determine which operation they need and use the calendar tool with the appropriate action:
List Calendars
Use calendar with action list to show all available calendars with their IDs and names.
List Events
Use calendar with action events to list events within a date range:
- Default: today through next 7 days
- Parameters:
calendar(filter by calendar),from(start date),to(end date),limit - Convenience parameters:
lastDays(N days ago),nextDays(N days ahead)
Get Event
Use calendar with action get to get full details for a specific event:
- Required:
id(event ID) - Returns complete event with recurrence rules, alarms, attendees
Search Events
Use calendar with action search to find events by title, notes, or location:
- Required:
query(search term) - Optional:
calendar,from,to,limit - Default search range: 30 days ago to 1 year from now
Create Event
Use calendar with action create to create a new event:
- Required:
title,start(date/time) - Optional:
endORduration(minutes),calendar,location,notes,allDay,alarm(minutes before),url,recurrence
Batch Create
Use calendar with action batch_create to create multiple events in one transaction:
- Required:
events(array of event objects, each with at leasttitleandstart) - More efficient for bulk operations (e.g., scheduling a week of meetings)
Update Event
Use calendar with action update to modify an existing event:
- Required:
id(event ID from list/search) - Optional:
title,start,end,location,notes,url,recurrence,futureEvents - For recurring events: use
futureEvents: trueto apply changes to all future occurrences - To remove recurrence: set
recurrence.frequencyto"none"
Delete Event
Use calendar with action delete to remove an event:
- Required:
id(event ID) - Optional:
futureEvents(default: false, only deletes single occurrence) - Safe for recurring events: default only removes one occurrence
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.
- 5d ago First seen · 136 lines · 18 tokens per session scan A 92a02270b72e
calendars is a command published in the GitHub repository omarshahine/apple-pim (51 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 1,453 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-31.
Other commands, from other repositories
quick-event
Quickly create a calendar event from natural language when the time and place are already known and stated directly. For deriving an event from a source — a meeting notice, an announcement, a message thread — where the time may have been corrected and the basis should be recorded, use the archive-event skill instead.
remind
Create a reminder from natural language.
week
Show this week's calendar overview.
today
Show today's calendar events and pending reminders.
check-tcc
Print che-ical-mcp's current TCC permission state, binary path, and ready-to-paste reset / re-prompt commands. Use when user says "check TCC", "permission status", "tccutil"。.
journal
Write a journal entry for today's work session on the rem project.