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 Vortx-AI/emem --skill emem-referential-driftgit clone --depth 1 https://github.com/Vortx-AI/ememWrote 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/vortx-ai/emem/emem-referential-drift)<a href="https://agentmods.dev/skills/vortx-ai/emem/emem-referential-drift"><img src="https://agentmods.dev/badge/skills/vortx-ai/emem/emem-referential-drift/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/vortx-ai/emem/emem-referential-drift"><img src="https://agentmods.dev/badge/skills/vortx-ai/emem/emem-referential-drift.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00124 | $0.01754 |
| Opus 5.5 | $0.00050 | $0.00702 |
| Sonnet 5.5 | $0.00025 | $0.00351 |
| Haiku 4.5 | $0.00012 | $0.00175 |
Grade A, and why
emem-referential-drift scanned grade A with 1 finding 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 17d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sf -X POST https://emem.dev/v1/recall \ How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
emem-referential-drift
Network use. The commands in this skill send and receive JSON (and, where a step says so, an image or a raster file) to
https://emem.devonly, the service the plugin's MCP server connects to. Nothing they download is executed. The files underscripts/read local files and make no network calls.
Referential drift has two sides. Words move: "the north field", "plot 14" and a cell64 turn out to be one object, or one phrase ends up meaning two. Values move: a number is copied, rounded, paraphrased and re-summarised until it arrives somewhere as a fact nobody can trace.
The words side is emem-shared-identity.
This skill is the values side.
Carry a token to the number, not the number
Every fact a recall returns already carries its citation in
memory_token. Take the one for the reading you mean; current_by_band
names the latest:
curl -sf -X POST https://emem.dev/v1/recall \
-H 'content-type: application/json' \
-d '{"cell":"defi.zb493.zezo.zcb35","bands":["weather.temperature_2m"]}' \
| jq -r '.current_by_band["weather.temperature_2m"] as $c
| .facts[] | select(.fact_cid == $c) | .memory_token'
facts[] is ordered oldest first, so .facts[0] is the oldest reading,
not the current one. If you hold a cell and a fact cid from somewhere
else, POST /v1/memory_token {"cell":..,"fact_cid":..,"band":..} builds
the same token (field memory_token) and adds the band's provenance
block.
The token is emem:fact:<cell64>:<fact_cid>. Any agent resolves it to
the byte-identical signed object:
curl -sf -X POST https://emem.dev/v1/memory_token/resolve \
-H 'content-type: application/json' \
-d '{"token":"emem:fact:defi.zb493.zezo.zcb35:nflpddk7zsncywguwjzk5koksseqfyx4jnngkuryrnd4aykqlpfq"}' \
| jq '{value_verbatim, unit, band, kind}'
Recorded on 2026-09-28: {"value_verbatim":"28.0","unit":"degC","band":"weather.temperature_2m","kind":"primary"}.
Quote value_verbatim, the exact decimal string that was signed;
re-typing the JSON number is where precision gets lost.
POST /v1/memory_token/resolve_many resolves a list in one call.
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.
- 17d ago Changed · +2 lines aecd2c370993
- 18d ago Changed · -13 lines · -8 tokens per session dad9811c1802
- 19d ago Changed · -1 lines 040b17fc6124
- 1mo ago First seen · 155 lines · 132 tokens per session scan A e40acbb8738d
emem-referential-drift is a skill published in the GitHub repository Vortx-AI/emem (71 stars, last pushed today), licensed Apache-2.0. It adds 124 tokens to every session and 1,754 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-17.
Other skills, from other repositories
mem0-cli
Mem0 CLI -- the command-line interface for mem0 memory operations. TRIGGER when: user mentions "mem0 cli", "mem0 command line", "@mem0/cli", "mem0-cli", "pip install mem0-cli", "npm install -g @mem0/cli", or is running mem0 commands in a terminal/shell (mem0 add, mem0 search, mem0 list, mem0 get, mem0 init, mem0…
mem0-vercel-ai-sdk
Mem0 provider for Vercel AI SDK (@mem0/vercel-ai-provider). TRIGGER when: user mentions "vercel ai sdk", "@mem0/vercel-ai-provider", "createMem0", "retrieveMemories", "addMemories", "getMemories", "searchMemories", "mem0 vercel", "AI SDK provider", "AI SDK memory", or is using generateText/streamText with mem0. Also…
mem0-tour
Browses all stored memories grouped by category with full content display. Use when reviewing all project memories, exploring stored knowledge, onboarding to a project, or getting an overview of captured decisions, conventions, and learnings.
mem0-scope
Views or changes the default memory scope (project, session, or global) used when saving and searching memories. Use when the user wants to control whether memories are scoped to this repo, this run, or shared across all their projects.
mem0-forget
Deletes memories by search query or memory ID with confirmation before removal. Use when removing outdated decisions, incorrect memories, sensitive data, or cleaning up after experiments. Also handles undo of recent additions.
mem0-remember
Stores a memory verbatim from user input with appropriate type classification and metadata. Use when the user says remember this, save this, store this, note that, or explicitly asks to record a decision, preference, convention, or learning.