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-emailgit 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-email)<a href="https://agentmods.dev/skills/markmhendrickson/neotoma/remember-email"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/remember-email/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/markmhendrickson/neotoma/remember-email"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/remember-email.svg" alt="Reviewed on agentmods" width="80" 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.00029 | $0.00835 |
| Opus 5 | $0.00015 | $0.00417 |
| Sonnet 5 | $0.00006 | $0.00167 |
| Haiku 4.5 | $0.00003 | $0.00084 |
Grade A, and why
remember-email 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 7d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remember Email
Import emails into Neotoma memory with full provenance. Extracts contacts, tasks, events, transactions, and other entities from email content.
When to use
When the user wants to persist emails and the entities they contain (contacts, commitments, tasks, events, financial transactions) into durable memory.
Prerequisites
Run the ensure-neotoma skill first if Neotoma is not yet installed or configured in your current harness.
An email MCP server must be configured (e.g. Gmail MCP). If one is not available, this skill guides the user through configuration.
Workflow
Phase 0: Verify Neotoma and email MCP
- Confirm Neotoma MCP is connected (call
get_session_identity). - Check if an email MCP is configured (e.g.
search_emailstool available). - If no email MCP is configured, guide the user:
- For Gmail: add the Gmail MCP server to the harness config and authenticate via OAuth.
- For other providers: check if an IMAP-capable MCP is available.
Phase 1: Discover emails
- Ask the user what to import:
- Recent emails (last N days/weeks)
- Emails from specific senders
- Emails matching a search query
- All emails in a folder/label
- Use
search_emailsto list matching messages. - Present a summary: count, date range, top senders.
Phase 2: Preview and confirm
- Show the user a preview of what will be imported:
- Number of emails
- Entity types that will be extracted (contacts, tasks, events, transactions)
- Estimated entities per email
- Ask for confirmation before proceeding.
Phase 3: Hydrate and extract
For each email (up to ~10 per turn, per depth-of-capture scope cap):
- Call the detail endpoint (
read_email) to get the full body, headers, and attachment metadata. - Extract entities from the email content:
- Contacts: sender, recipients, anyone mentioned by name+email
- Tasks: action items, requests, commitments ("please send", "I need", deadlines)
- Events: meetings, calls, scheduled items with dates
- Transactions: invoices, receipts, payment confirmations with amounts and currencies
- Set
data_sourceper email using the message ID:"Gmail read_email id=<message_id> <ISO-date>" - Include
source_quoteon each extracted entity with the relevant snippet from the email body.
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.
- 7d ago First seen · 90 lines · 29 tokens per session scan A 34d48b0130cc
remember-email is a skill published in the GitHub repository markmhendrickson/neotoma (32 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 835 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
remember
Routes user requests containing "remember", "recall", "checkpoint", "session", "todo", or "where were we" to the correct OpenEmpiric (OEM) MCP tool. Use when the user wants to persist, retrieve, or contextualize knowledge from project memory.
akf
Trust metadata for files, memories, and skills — check before you trust, stamp what you verify. A stamp costs 15 tokens; re-verifying costs 15,000.
akf
Trust metadata for files, memories, and skills — check before you trust, stamp what you verify. Use before building on existing files, after completing verified work, and when handling agent memories or downloaded skills.
aoa-memo
AoA/Abyss durable memory and owner orientation: use when ongoing work may depend on reviewed prior decisions, provenance, lifecycle/currentness, or an existing memo artifact, even when none is named. Also use to recall, review, or evolve a candidate, export, quarantine packet, object, corpus identity, lifecycle…
soul-archive
Soul Archive — A digital personality persistence system + agentic memory. Builds your digital soul clone through everyday AI conversations, with proactive context injection, cross-session recall, failure-pattern warning, and pattern distillation. All data stored locally as plaintext JSON. Six modes: Soul Extract, Soul…
mk:wiki
Capture, gate, query, and render long-term project knowledge through the gated mewkit wiki subsystem. Use to create a wiki, propose/approve candidates (scanner-gated), hand off a skill's terminal artifact as a scanned candidate, recall context, search the FTS index, or list pages. Agents may only PROPOSE candidates…