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-contactsgit 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-contacts)<a href="https://agentmods.dev/skills/markmhendrickson/neotoma/remember-contacts"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/remember-contacts/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-contacts"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/remember-contacts.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.00027 | $0.00732 |
| Opus 5 | $0.00014 | $0.00366 |
| Sonnet 5 | $0.00005 | $0.00146 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
remember-contacts 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 8d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remember Contacts
Consolidate contacts from multiple sources — email, calendar, chat, vCards, LinkedIn exports — into Neotoma memory. Deduplicates by name and email to build a unified contact graph.
When to use
When the user wants to build a persistent, deduplicated contact list from various data sources.
Prerequisites
Run the ensure-neotoma skill first if Neotoma is not yet installed or configured in your current harness.
Supported sources
| Source | Format | Method |
|---|---|---|
| Gmail/IMAP headers | Email MCP (extract sender/recipient) | |
| Calendar | Event attendees | Calendar MCP |
| vCards | .vcf files |
File read |
| CSV export | File read | |
| Chat history | Conversation participants | File read |
| Manual | User-stated contacts | Chat extraction |
Workflow
Phase 0: Verify Neotoma
Confirm Neotoma MCP is connected (call get_session_identity).
Phase 1: Identify sources
- Ask the user which sources to pull contacts from:
- Email (requires email MCP)
- Calendar (requires calendar MCP)
- vCard file
- LinkedIn export CSV
- Chat history files
- For MCP-based sources, verify the relevant MCP is configured.
Phase 2: Collect and deduplicate
- Email MCP: extract unique sender/recipient pairs from recent emails.
- Calendar MCP: extract attendees from recent events.
- vCard files: parse
.vcffiles for name, email, phone, organization. - LinkedIn CSV: parse the connections export for name, title, company, email.
- Chat history: extract participants from conversation files.
Before storing each contact, check for existing records:
- Search by email address first (most unique).
- Search by name if no email match.
- If a match exists, use
correctto update with new fields rather than creating a duplicate.
Phase 3: Preview and confirm
Present the consolidated contact list:
- Total contacts found per source
- Duplicates detected and merged
- New contacts to be created Ask for confirmation before storing.
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.
- 8d ago First seen · 97 lines · 27 tokens per session scan A 7a724fcc76b4
remember-contacts is a skill published in the GitHub repository markmhendrickson/neotoma (32 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 732 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.
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…
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…
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…