setup-calendar

A setup skill that installs and configures ical, a command-line tool for managing Apple Calendar on macOS. It checks the installation, requests Calendar permission, and verifies access.

In plain words
What is it for?
Use it when preparing a new Mac for Apple Calendar management, or when ical is installed but lacks permission.
Why use it?
It guides you through the command-line tool and macOS permission steps needed before calendar actions can work. It avoids reinstalling ical when it is already working.

Skill for Claude CodeCodex

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 skills/ericboehs/claude-plugins/setup-calendar
Any agent
npx skills add ericboehs/claude-plugins --skill setup-calendar
Clone the repo
git clone --depth 1 https://github.com/ericboehs/claude-plugins

Made for: Claude Code, Codex.

Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 370 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 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.00034 $0.00370
Opus 5 $0.00017 $0.00185
Sonnet 5 $0.00007 $0.00074
Haiku 4.5 $0.00003 $0.00037

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

Security

Grade C, and why

setup-calendar scanned grade C with 2 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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

curl -fsSL https://ical.sidv.dev/install | bash

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -fsSL https://ical.sidv.dev/install | bash
plugins/apple-calendar-setup/skills/setup-calendar/SKILL.md · 58 lines

What it actually says

Setup Apple Calendar CLI

Guided installation of the ical CLI tool for managing Apple Calendar from the command line.

Step 1: Check Prerequisites

which ical && ical version

If ical is already installed, tell the user their calendar CLI is ready and suggest /calendar.

Step 2: Install ical

curl -fsSL https://ical.sidv.dev/install | bash

This installs the ical binary to /usr/local/bin/ical.

Step 3: Grant Calendar Access

The first time ical runs, macOS will prompt for Calendar access. Run a test command to trigger the permission dialog:

ical calendars

If the user sees a permissions error, guide them to:

  1. Open System Settings > Privacy & Security > Calendars
  2. Enable access for the terminal app they're using (Terminal, iTerm2, Ghostty, etc.)
  3. Re-run ical calendars

Step 4: Verify

# List calendars
ical calendars

# Show today's events
ical today -o json

If both commands succeed, the setup is complete. Suggest the user try /calendar.

Behavior

  1. Run through steps sequentially, checking what's already done
  2. Don't reinstall if ical is already present and working
  3. If ical is installed but calendar access is denied, focus on the permissions step
  4. After successful setup, suggest /calendar to start using it
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 · 58 lines · 34 tokens per session scan C b48521424c97

Subscribe to this mod's changes

setup-calendar is a skill published in the GitHub repository ericboehs/claude-plugins (2 stars, last pushed 8d ago), licensed MIT. It adds 34 tokens to every session and 370 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens