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 query-memorygit 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/query-memory)<a href="https://agentmods.dev/skills/markmhendrickson/neotoma/query-memory"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/query-memory/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/query-memory"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/query-memory.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.00019 | $0.00490 |
| Opus 5 | $0.00010 | $0.00245 |
| Sonnet 5 | $0.00004 | $0.00098 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
query-memory 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Query Neotoma Memory
When to use
When the user asks about previously stored information, wants to recall facts, explore relationships, or view a timeline of events.
Retrieval strategy
Start with narrow, targeted queries and expand only on ambiguity or low confidence.
By identifier (names, emails, specific items)
Use retrieve_entity_by_identifier first:
- Fast lookup by name, email, tax_id, or any canonical identifier.
- Optionally scope to a specific
entity_type.
By type or category
Use retrieve_entities with filters:
entity_type: filter to a specific type (task, contact, event, transaction).search: free-text semantic search across all fields.published_after/published_before: date range filters.sort_by/sort_order: control ordering.limit/offset: pagination.
By time
Use list_timeline_events for chronological queries:
- Filter by event type, date range, or source.
- Returns events derived from date fields in stored data.
By relationships
Use retrieve_related_entities to traverse the entity graph:
- Start from a known entity and follow relationship links.
- Control direction (inbound, outbound, both) and hop count.
Use retrieve_graph_neighborhood for a full picture:
- Returns related entities, relationships, sources, and events around a node.
Entity details
Use retrieve_entity_snapshot for the full current state of a single entity with provenance.
Use list_observations to see the complete history of changes.
Use retrieve_field_provenance to trace a specific field back to its source.
Response format
When displaying retrieved entities, show a Markdown table per entity with all substantive fields. Use human-readable property names (snake_case to Title Case). Omit opaque internal IDs.
Do not
- Run broad unfiltered queries when a specific identifier is available.
- Invent or hallucinate memory-backed claims when retrieval finds nothing.
- Skip the relationship graph when the user asks about connections between entities.
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 · 68 lines · 19 tokens per session scan A 21a8f4936a8e
query-memory is a skill published in the GitHub repository markmhendrickson/neotoma (32 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 490 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…