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.
git 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/plugins/vortx-ai/emem/emem-signer)<a href="https://agentmods.dev/plugins/vortx-ai/emem/emem-signer"><img src="https://agentmods.dev/badge/plugins/vortx-ai/emem/emem-signer/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/plugins/vortx-ai/emem/emem-signer"><img src="https://agentmods.dev/badge/plugins/vortx-ai/emem/emem-signer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
emem-signer 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 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.
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.
What it actually says
{
"name": "emem-signer",
"description": "A local signer for emem memory writes. It holds your Ed25519 signing key, given as a sensitive plugin option, and signs only the writes you compose. Optional: install it beside the emem plugin when you want to write signed notes; reading emem needs no key.",
"version": "2.4.4",
"author": {
"name": "Vortx AI",
"email": "[email protected]",
"url": "https://vortx.ai"
},
"homepage": "https://emem.dev",
"repository": "https://github.com/Vortx-AI/emem",
"license": "Apache-2.0",
"keywords": [
"emem",
"ed25519",
"signing",
"agent-memory"
],
"icon": "icon.png",
"privacyPolicyUrl": "https://emem.dev/privacy",
"userConfig": {
"signing_seed_hex": {
"type": "string",
"title": "Signing key",
"description": "The 32-byte Ed25519 seed that signs your emem memory writes, as 64 hex characters. It is stored in your secure credential store and given only to the local emem-signer process.",
"sensitive": true,
"required": false
}
}
}
What it installs
The manifest is a name and a version. 1 MCP server travel with it, and installing the plugin installs all of them. Each is measured on its own page, and each can be installed alone.
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 First seen · 31 lines scan A 991e7e9e7b42
emem-signer is a plugin published in the GitHub repository Vortx-AI/emem (72 stars, last pushed yesterday), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-10-21.
Other plugins, from other repositories
mem0
Cross-session memory and token savings for coding agents.
obsidian-wiki
Grow an Obsidian second brain with your AI agent: ingest docs, chat history and URLs into interlinked markdown, then query it with citations. Karpathy's LLM Wiki pattern as Claude Code skills.
hippo-memory
Make your agent's memory work like a brain. Hippo is long-term memory for coding agents.
kairn
A local knowledge graph with full-text recall, started by the client over stdio, with no LLM call needed to save or recall.
goodmem
GoodMem memory infrastructure for AI agents. Use Python SDK skills to write code that manages embedders, spaces, and memories, or use MCP tools to perform GoodMem operations directly via natural language.
runtime-memory
Persistent memory with outcome-based learning for AI coding agents. Stores knowledge from coding sessions, learns which memories actually help, and gets smarter over time.