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/configuregit 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/configure)<a href="https://agentmods.dev/commands/omarshahine/apple-pim/configure"><img src="https://agentmods.dev/badge/commands/omarshahine/apple-pim/configure.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.00013 | $0.01268 |
| Opus 5 | $0.00006 | $0.00634 |
| Sonnet 5 | $0.00003 | $0.00254 |
| Haiku 4.5 | $0.00001 | $0.00127 |
Grade A, and why
configure 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 6d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configure Apple PIM Access
Apple PIM is the Personal Information Manager plugin for Calendar, Reminders, Contacts, and Mail.
Help the user configure which domains, calendars, and reminder lists the apple-pim plugin can access.
Tip: If you encounter permission errors during configuration, use /apple-pim:authorize to check and request macOS permissions first.
Configuration Location
The config file is at ~/.config/apple-pim/config.json (JSON format).
The Swift CLIs read this file directly via the PIMConfig library.
Do NOT write to any plugin cache directory or use YAML/markdown format.
Process
- Check permissions with
apple-pimactionconfig_showto see current config and actionstatusfor macOS access- If any domain shows
notDetermined, use actionauthorizeto trigger prompts - If any domain shows
denied, warn the user and guide to System Settings
- If any domain shows
- Discover available items with
apple-pimactionconfig_init— this lists ALL calendars and reminder lists from macOS - Read existing config from
~/.config/apple-pim/config.jsonif it exists - Ask which domains to enable (Calendars, Reminders, Contacts, Mail) — multi-select
- For enabled domains with filtering (Calendars, Reminders):
- Use the discovery data from
apple-pimactionconfig_init(do NOT usecalendaractionlist— that returns filtered results) - Ask user which to allow
- Use the discovery data from
- Set defaults for new events/reminders
- Write config file as JSON to
~/.config/apple-pim/config.json - Confirm changes are effective immediately (no restart needed)
Configuration File Format
Write the config file as JSON to ~/.config/apple-pim/config.json:
{
"calendars": {
"enabled": true,
"mode": "allowlist",
"items": ["Calendar Name 1", "Calendar Name 2"]
},
"reminders": {
"enabled": true,
"mode": "allowlist",
"items": ["List Name 1", "List Name 2"]
},
"contacts": {
"enabled": true,
"mode": "all",
"items": []
},
"mail": {
"enabled": true
},
"default_calendar": "Calendar Name",
"default_reminder_list": "List Name"
}
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.
- 6d ago First seen · 116 lines · 13 tokens per session scan A 2086431b77fc
configure is a command published in the GitHub repository omarshahine/apple-pim (51 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 1,268 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
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"。.
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.
today
Show today's calendar events and pending reminders.
week
Show this week's calendar overview.
prep-for-task
Bootstrap context for a new session on the rem project. Run this BEFORE starting any implementation work.