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/neotoma --skill remember-calendargit clone --depth 1 https://github.com/markmhendrickson/neotomaWrote 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/neotoma/remember-calendar)<a href="https://agentmods.dev/skills/markmhendrickson/neotoma/remember-calendar"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/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.00021 | $0.00681 |
| Opus 5 | $0.00010 | $0.00341 |
| Sonnet 5 | $0.00004 | $0.00136 |
| Haiku 4.5 | $0.00002 | $0.00068 |
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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remember Calendar
Import calendar events into Neotoma memory — either from a live calendar MCP or from ICS file exports. Extracts scheduling commitments, attendees, and recurring patterns.
When to use
When the user wants to persist calendar events, scheduling commitments, and associated contacts into durable memory.
Prerequisites
Run the ensure-neotoma skill first if Neotoma is not yet installed or configured in your current harness.
Supported sources
| Source | Format | Method |
|---|---|---|
| Google Calendar | Live API | Google Calendar MCP |
| Apple Calendar | ICS export | File read |
| Outlook | ICS export | File read |
| Any calendar | .ics files |
File read |
Workflow
Phase 0: Verify Neotoma
Confirm Neotoma MCP is connected (call get_session_identity).
Phase 1: Identify source
- Check if a calendar MCP is configured (e.g.
list_eventstool available). - If no MCP, ask the user for an ICS file path.
- For MCP: ask for a time range (default: past 30 days + next 30 days).
- For ICS: read the file to determine the date range available.
Phase 2: Retrieve and preview
- Calendar MCP: use
list_eventsto retrieve events in the specified range. - ICS file: parse the iCalendar format to extract events.
- Present a preview: event count, date range, recurring vs one-time, top attendees.
- Ask for confirmation.
Phase 3: Extract entities
For each event:
- Event: create an
evententity withtitle,start_time,end_time,location,description,recurrence. - Contacts: extract attendees as
contactentities (deduplicate against existing contacts). - Tasks: for events with action-oriented titles or descriptions, create associated tasks.
- Places: extract locations as
placeentities when they are specific venues.
For MCP sources, hydrate via the detail endpoint (get_event) before persisting, and set data_source per event with the event ID.
Phase 4: Store with provenance
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 · 86 lines · 21 tokens per session scan A 149cb7a6d875
remember-calendar is a skill published in the GitHub repository markmhendrickson/neotoma (31 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 681 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-09-03.
Other skills, from other repositories
Migrate
Intakes external content, classifies chunks against LifeOS taxonomy, commits with provenance. Sources: .md/.txt, stdin, LifeOS dirs, CLAUDE.md/Cursor/OpenAI Custom Instructions, Obsidian/Notion/Apple Notes exports. MigrateScan classifies → routing table. MigrateApprove with…
daily-briefing
Proactive daily briefing that fires on a recurring schedule, pulls recent memory and workspace context, composes a structured summary (action items, progress, radar, next steps), and delivers it to all active channels. Enable with a time like "set up my daily briefing at 9am". Disable, reschedule, or check status at…
company-brain
Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so Claude can answer questions on your team's behalf. Team-scope sibling to second-brain (which is personal-scope). Seven modes — capture (drop something into the right structured dir), compile (process into wiki…
dbrain-processor
Personal assistant for processing daily voice/text entries from Telegram. Classifies content, saves thoughts to Obsidian with wiki-links, generates HTML reports. Integrates Your Business context (clients, projects, CRM). Triggers on /process command or daily 21:00 cron.
cortex-profile
View and manage your cognitive profile — how you think, work patterns, blind spots, and cross-domain connections. Use when the user says 'show my profile', 'how do I work', 'what are my patterns', 'cognitive style', 'blind spots', 'methodology', or at the start of a session to load context. Also use 'rebuild profile'…
operator
Build and schedule a personalized Operator prompt that runs a Baalda vault as a second brain on a recurring cadence. Run it from inside the vault: it reads Context/ and CLAUDE.md first to infer org, team, brand voice and paths, then asks only the gaps (cadence, connectors, DM recipient, budgets, signature), writes the…