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 skills/jansenanalytics/claudex/calendar-managernpx skills add JansenAnalytics/claudex --skill calendar-managergit clone --depth 1 https://github.com/JansenAnalytics/claudexWrote 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/skills/jansenanalytics/claudex/calendar-manager)<a href="https://agentmods.dev/skills/jansenanalytics/claudex/calendar-manager"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/calendar-manager.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 | $0.00022 | $0.00644 |
| Opus 5 | $0.00011 | $0.00322 |
| Sonnet 5 | $0.00004 | $0.00129 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
calendar-manager 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 4d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
calendar-manager
Read and manage Google Calendar events: list upcoming, create events, check availability, send reminders.
When to Use
- Checking calendar for upcoming events
- Creating new calendar events
- Finding free time slots / checking availability
- Parsing .ics (iCalendar) files
- Setting up meeting reminders
- Integrating calendar with other workflows
Scripts
scripts/gcal-helper.py
Google Calendar API helper — list events, check availability.
# List upcoming events (dry-run with sample data)
python3 scripts/gcal-helper.py --dry-run --list --days 7
# List events (live, requires credentials.json)
python3 scripts/gcal-helper.py --list --days 3
# Check availability for a date range
python3 scripts/gcal-helper.py --dry-run --free --date 2026-03-10 --duration 60
Requires: credentials.json from Google Cloud Console for live mode.
scripts/event-creator.py
Create Google Calendar events.
# Create event (dry-run)
python3 scripts/event-creator.py --dry-run --title "Team Standup" \
--start "2026-03-10T09:00:00" --end "2026-03-10T09:30:00" \
--attendees "[email protected],[email protected]"
# Create event (live)
python3 scripts/event-creator.py --title "Lunch" --start "2026-03-10T12:00:00" --end "2026-03-10T13:00:00"
scripts/ical-parser.py
Parse .ics files and extract event details.
# Parse an .ics file
python3 scripts/ical-parser.py path/to/calendar.ics
# Parse from stdin
cat meeting.ics | python3 scripts/ical-parser.py -
# Dry-run with built-in sample
python3 scripts/ical-parser.py --dry-run
References
references/gcal-api-quickstart.md— Google Calendar API setup guidereferences/oauth2-setup.md— OAuth2 configuration for Google APIsreferences/ical-format.md— iCalendar format reference
Requirements
- Python 3.8+
- No pip dependencies for ical-parser (stdlib only)
- Google Calendar API scripts need
google-api-python-client,google-auth-oauthlibfor live mode - Dry-run mode works without any dependencies
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.
- 4d ago First seen · 88 lines · 22 tokens per session scan A 5be9258247e3
calendar-manager is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 644 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 skills, from other repositories
calendar-scheduling
Use when a product needs a booking surface — a pick-a-slot page, a Cal.com/Calendly embed, or real availability plus the confirmed meeting written to Google/Outlook — or when fixing double-booking, DST drift, or orphaned reschedule events. NOT calendar CRUD with no booking surface (that is google-workspace), NOT the…
calendar-automation
Google Calendar and Outlook automation - scheduling optimization, meeting workflows, time blocking, and Slack/Sheets integration.
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
managing-google-workspace
Manages Google Workspace operations across 12 services (Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Contacts, Chat, Apps Script, Custom Search). Supports MCP tools or CLI via uvx workspace-mcp --cli. Provides tool routing, workflows, and parameter guidance for 114 tools. Triggers for "check my email"…
remindme
⏰ simple Telegram reminders for OpenClaw. cron, zero dependencies.
remctl
Use when an agent needs to read, create, edit, complete, inspect, or troubleshoot Apple Reminders through the RemCTL CLI on macOS.