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/aayoawoyemi/Ori-MnemosWrote 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/mcp/aayoawoyemi/ori-mnemos/ori-memory)<a href="https://agentmods.dev/mcp/aayoawoyemi/ori-mnemos/ori-memory"><img src="https://agentmods.dev/badge/mcp/aayoawoyemi/ori-mnemos/ori-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/mcp/aayoawoyemi/ori-mnemos/ori-memory"><img src="https://agentmods.dev/badge/mcp/aayoawoyemi/ori-mnemos/ori-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ori-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 11d 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.
What it actually says
{
"ori-memory": {
"command": "npx",
"args": [
"-y",
"ori-memory"
],
"env": {}
}
}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.
- 11d ago First seen · 10 lines scan A a16a42afaba9
ori-memory is an MCP server published in the GitHub repository aayoawoyemi/Ori-Mnemos (323 stars, last pushed 1mo ago), licensed Apache-2.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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-08-30.
Other mcp servers, from other repositories
honcho
Memory that reasons: continual learning for stateful agents. Better context, fewer tokens. Remote server at mcp.honcho.dev.
plur
Open, local-first engram memory for AI agents: read, correct, delete; shared over MCP. Runs locally from the @plur-ai/mcp npm package.
deepmem
Mem0-compatible persistent memory for AI agents: write facts once, recall them semantically. Remote server at deepmem.dev.
anneal-memory
Living memory for AI agents. Episodes compress into identity. Runs locally from the anneal-memory Python package.
genome
DNA-inspired memory layer for AI agents: zero-LLM-call ingestion, retrieval that beats full-context on overflowing histories. Runs locally from the genome-memory Python package.
universal-memory
MCP server "universal-memory", hosted remotely at localhost, as configured in goldenwo/universal-memory.