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-shared-identitygit 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-shared-identity)<a href="https://agentmods.dev/skills/vortx-ai/emem/emem-shared-identity"><img src="https://agentmods.dev/badge/skills/vortx-ai/emem/emem-shared-identity/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-shared-identity"><img src="https://agentmods.dev/badge/skills/vortx-ai/emem/emem-shared-identity.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.00123 | $0.01861 |
| Opus 5.5 | $0.00049 | $0.00744 |
| Sonnet 5.5 | $0.00025 | $0.00372 |
| Haiku 4.5 | $0.00012 | $0.00186 |
Grade A, and why
emem-shared-identity 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 today.
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/entity/resolve \ How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
emem-shared-identity
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.
This is the words half of referential drift. The values half, where a
number is paraphrased until nobody can trace it, is
emem-referential-drift.
Two agents studying one farm call it "plot 14", "the Dhaulana parcel"
and defi.zb64a.cAzU.zfa27. Nothing in their measurements disagrees;
their words do. The identity surface collapses that into one object with
one emem:entity:<cid> token that either agent resolves to the same
thing.
The calls, in the order to use them
- Resolve (open, no key):
POST /v1/entity/resolve(MCPemem_entity_resolve) converges a phrasing onto identities that already exist. - Link (T3):
POST /v1/entity/alias(MCPemem_entity_link) records a signed, attributed claim that a label or external id (GERS, OSM, Wikidata) denotes an existing object, or withstance: "disputes"that it does not. Resolve ranks candidates by how many independent keys agree, so one key's link reads as one key's claim. - Mint (T3):
POST /v1/entity(MCPemem_entity) creates the canonical identity, idempotently: the same anchor returns the same token withcreated: false.
Fetch one by id with GET /v1/entity/<entity_cid>.
Resolve first. Minting first is how a registry collects several identities for one object, and that has already happened:
curl -sf -X POST https://emem.dev/v1/entity/resolve \
-H 'content-type: application/json' \
-d '{"text":"Mount Fuji","k":3}' \
| jq '[.candidates[] | {entity_token, kind: .entity.kind, cell64: .entity.cell64,
corroboration, disputed_by}]'
On 2026-09-28 that returned three distinct tokens for "Mount Fuji" (two
of kind place, one volcano), all at cell defi.zb5ff.pOyA.zaf69,
each with corroboration: "none_attributed". The right move there is to
pick one, link your phrasing (and its Wikidata or OSM id) to it, and not
mint a fourth. Say which one you chose and why.
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.
- today Changed · +16 lines d2673c429208
- 17d ago Changed · +2 lines 6413fcd724e7
- 18d ago Changed · +5 lines 6750148803de
- 19d ago Changed · -1 lines 6ce2a48eceb3
- 1mo ago First seen · 118 lines · 123 tokens per session scan A d1ff7c2b8837
emem-shared-identity is a skill published in the GitHub repository Vortx-AI/emem (71 stars, last pushed today), licensed Apache-2.0. It adds 123 tokens to every session and 1,861 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.