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/lvndry/jazz/calendarnpx skills add lvndry/jazz --skill calendargit clone --depth 1 https://github.com/lvndry/jazzWrote 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/lvndry/jazz/calendar)<a href="https://agentmods.dev/skills/lvndry/jazz/calendar"><img src="https://agentmods.dev/badge/skills/lvndry/jazz/calendar.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.00089 | $0.01206 |
| Opus 5 | $0.00044 | $0.00603 |
| Sonnet 5 | $0.00018 | $0.00241 |
| Haiku 4.5 | $0.00009 | $0.00121 |
Grade B, and why
calendar scanned grade B 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 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
3. `curl -s -X POST https://oauth2.googleapis.com/token -d "code=$CODE" -d "client_id=$CID" -d "client_secret=$CSEC" -d "redirect_uri=http://localhost:8080" -d "grant_type=authorization_code"`. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
3. `curl -s -X POST https://oauth2.googleapis.com/token -d "code=$CODE" -d "client_id=$CID" -d "client_secret=$CSEC" -d "redirect_uri=http://localhost:8080" -d "grant_type=authorization_code"`. How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Calendar Management
Two backends:
- khal + vdirsyncer for CalDAV providers (Nextcloud, iCloud, Fastmail, Radicale…).
- gcalcli for Google Calendar — Google's CalDAV endpoint rejects the discovery handshake and app-password Basic Auth, so khal/vdirsyncer cannot be used for it.
khal (non-Google CalDAV)
vdirsyncer syncfirst to refresh local data. Skip entirely if this is a Google-only setup (no working vdirsyncer pair). Ifkhal printcalendarserrors or lists nothing, fall back to gcalcli.khal list today|week|<range>— read.khal list --format "{start} {end} {title}"for parsing.khal new "Team meeting tomorrow 3pm-4pm"— natural language, or structured:khal new -a work 2026-02-15 14:00 1h "Sprint Planning" --location "Room A".khal search "meeting"returns UIDs →khal edit <uid>/khal delete <uid>.khal printcalendarslists calendars;-a <cal>targets one.- Setup/config details: see references/providers.md.
gcalcli (Google)
Isolation is by data dir only — there is no --account flag. Each account needs its own $XDG_DATA_HOME (e.g. ~/.local/share/gcalcli-account-a); reusing one dir overwrites the previous account's cache.
Before OAuth, check for an already-configured account — gcalcli's cache is $XDG_DATA_HOME/gcalcli/oauth, and many deployments set $XDG_DATA_HOME to a non-default path, so an empty ~/.local/share does NOT mean no account exists:
find "${XDG_DATA_HOME:-$HOME/.local/share}"/.. -maxdepth 2 -iname "gcalcli*".
Use a found dir directly: XDG_DATA_HOME=<dir> gcalcli agenda.
One-time OAuth client (per deployment): Google Cloud Console → enable Calendar API → OAuth consent (External, add each user as test user) → create a Desktop-app client ID/secret. Reuse the same client across all accounts.
Per account (repeat for each): XDG_DATA_HOME=~/.local/share/gcalcli-account-a gcalcli --client-id "$CID" --client-secret "$CSEC" init.
If init hangs after Allow (browser opens two connections, the callback server grabs the wrong one), recover manually per account:
- Open
https://accounts.google.com/o/oauth2/auth?response_type=code&client_id=$CID&redirect_uri=http://localhost:8080&scope=https://www.googleapis.com/auth/calendar&access_type=offline&prompt=select_account%20consent&login_hint=$EMAIL.prompt=select_account consentis REQUIRED with >1 account, or Google silently reuses the logged-in account and writes the wrong token. - Copy
codefrom the failedhttp://localhost:8080/?...&code=...URL. curl -s -X POST https://oauth2.googleapis.com/token -d "code=$CODE" -d "client_id=$CID" -d "client_secret=$CSEC" -d "redirect_uri=http://localhost:8080" -d "grant_type=authorization_code".- Write JSON
{access_token, client_id, client_secret, refresh_token, token_uri:"https://oauth2.googleapis.com/token", scopes:[...]}to$XDG_DATA_HOME/gcalcli/oauth. - Verify:
XDG_DATA_HOME=~/.local/share/gcalcli-account-a gcalcli listshows THAT account's calendars, not another's.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 49 lines · 89 tokens per session scan B 77dbf218ddcd
calendar is a skill published in the GitHub repository lvndry/jazz (51 stars, last pushed yesterday), licensed MIT. It adds 89 tokens to every session and 1,206 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
channel_message
Use this skill to proactively send a one-way message to a user/session/channel, usually only when the user explicitly asks to send to a channel/session or when proactive notification is needed. First query sessions with qwenpaw chats list, then push with qwenpaw channels send.
tmux
Remote-control tmux sessions for interactive CLIs by sending keystrokes, capturing pane output, and managing terminal multiplexer windows. Enables parallel coding-agent orchestration, background process management, and REPL interaction via sockets. Use when the agent needs to launch, monitor, or coordinate…
local-tools
Access local system resources including Calendar on macOS and Windows. Use this skill when you need to manage user's schedule directly on their device.
apple-reminders
Manage Apple Reminders via the remindctl CLI on macOS (list, add, edit, complete, delete). Supports lists, date filters, and JSON/plain output. Use when the user asks about reminders, todos, tasks, to-do lists, "remind me", scheduling tasks, checking what is due today, completing or deleting reminders, or managing…
obsidian
Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli. Use when the user asks about notes, vault management, PKM, knowledge base organization, wikilinks, or personal knowledge management in Obsidian.
things-mac
Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks Otto to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.