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/ondrasek/cc-plugins/vault-calendarnpx skills add ondrasek/cc-plugins --skill vault-calendargit clone --depth 1 https://github.com/ondrasek/cc-pluginsWrote 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/ondrasek/cc-plugins/vault-calendar)<a href="https://agentmods.dev/skills/ondrasek/cc-plugins/vault-calendar"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/vault-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.00052 | $0.00781 |
| Opus 5 | $0.00026 | $0.00391 |
| Sonnet 5 | $0.00010 | $0.00156 |
| Haiku 4.5 | $0.00005 | $0.00078 |
Grade A, and why
vault-calendar 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vault Calendar
Critical Rules
- Never store credentials in the vault — calendar auth is handled externally by the user (OAuth2 for Google,
az loginfor Microsoft) - Always confirm with user before writing to daily notes — show the formatted events and target file path before inserting
- Adapt format to vault's daily note template structure — detect existing sections and insert schedule content in the appropriate location
Context Files
Read these files before starting:
skills/vault-calendar/references/calendar-providers.md— provider detection, CLI commands, response parsingskills/vault-calendar/references/daily-note-format.md— event formatting, daily note detection, section insertion rules
Workflow
1. Detect Calendar Provider
Check which calendar CLI tools are available:
- Google Calendar:
command -v gcalcli - Microsoft 365:
command -v azandaz account show
If neither is available, report which tools to install and how to authenticate. Do not proceed without a working provider.
2. Detect Daily Notes Configuration
Read vault configuration to find daily note settings:
- Check
.obsidian/daily-notes.jsonfor folder, format, and template settings - Check
.obsidian/community-plugins.jsonfor Periodic Notes plugin - If Periodic Notes is active, check
.obsidian/plugins/periodic-notes/data.jsoninstead - Fall back to defaults: root folder,
YYYY-MM-DDformat, no template
3. Fetch Events for Target Date
Fetch calendar events for the specified date (default: today):
- Use provider-specific commands from
calendar-providers.md - Parse the response into a structured list of events
- Handle edge cases: all-day events, multi-day events, no events found
4. Format Events as Markdown
Format events following the patterns in daily-note-format.md:
- Adapt to the vault's daily note template if one exists
- Use 24h time format by default, adapt to vault convention if detected
- Include location and description where available
What ships with it
2 files 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 · 78 lines · 52 tokens per session scan A f34f21399d8c
vault-calendar is a skill published in the GitHub repository ondrasek/cc-plugins (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 52 tokens to every session and 781 once invoked, about $0.0003 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
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.