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 skills add markmhendrickson/ateles --skill remember-calendargit clone --depth 1 https://github.com/markmhendrickson/atelesWrote 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/markmhendrickson/ateles/remember-calendar)<a href="https://agentmods.dev/skills/markmhendrickson/ateles/remember-calendar"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/remember-calendar.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00000 | $0.01171 |
| Opus 5 | $0.00000 | $0.00585 |
| Sonnet 5 | $0.00000 | $0.00234 |
| Haiku 4.5 | $0.00000 | $0.00117 |
Grade A, and why
remember-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 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: remember-calendar description: Proactively sync Neotoma event entities to Google Calendar, routing each event to the correct calendar per the operator's calendar_routing_config. Runs without being asked whenever a new event entity lacks a google_event_id. user_invocable: true triggers:
- remember-calendar
- /remember-calendar
- add to calendar
- sync to calendar
- put in calendar supported_harnesses:
- claude_code entity_id: ent_2180e21ca95d095fd30e4f84
remember-calendar — Neotoma ↔ Google Calendar Sync
Purpose
Keep Neotoma event entities and Google Calendar in sync. The canonical record is Neotoma; Google Calendar is the display layer. Each event routes to a calendar based on its type, following the operator's routing config (retrieved at runtime — see below).
Calendar routing (retrieve at runtime, never hardcode)
Calendar IDs and the personal routing rules are operator-specific, so they are not in this skill. At runtime, retrieve the calendar_routing_config entity named operator-calendar-routing from Neotoma and follow its routing table: each entry gives a calendar_id and the use_when conditions that select it, with one entry flagged is_default for the uncertain case. Use the is_default calendar when classification is ambiguous. After creating or updating an event, write back the fields named in the config's writeback_fields using its writeback_idempotency_pattern.
If the config entity is missing, stop and surface that rather than guessing a calendar.
Trigger conditions (proactive)
Apply this skill without being asked whenever:
- A new
evententity is stored in Neotoma and it lacks agoogle_event_idfield - An event entity is corrected (date/time/location changed) and it has a
google_event_id— update the GCal event - The user shares a message, screenshot, or invitation containing event details
- A task is created with a due_date and a clear venue/meeting (create a calendar block)
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 · 103 lines · 0 tokens per session scan A e638794fe0cb
remember-calendar is a skill published in the GitHub repository markmhendrickson/ateles (6 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,171 tokens. 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-09-03.
Other skills, from other repositories
life-automation-audit
Use this as an on-demand long prompt. Do not paste it into SOUL.md / PRINCIPLES.md / AGENTS.md. When the user asks to audit their life for automation opportunities, load and follow this prompt.
discord
Control Discord via the discord tool: manage messages, reactions, polls, channels, and bot presence.
slack
Use when you need to control Slack from Kabot via the slack tool, including reacting to messages or pinning/unpinning items in Slack channels or DMs.
bluebubbles
Use when you need to send or manage iMessages via BlueBubbles (recommended iMessage integration). Calls go through the generic message tool with channel="bluebubbles".
notion
Notion API for creating and managing pages, databases, and blocks.
himalaya
CLI to manage emails via IMAP/SMTP. Use himalaya to list, read, write, reply, forward, search, and organize emails from the terminal. Supports multiple accounts and message composition with MML (MIME Meta Language).