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/skynetcmd/m3-memoryInstalling this writes the configuration, not the program: `m3` has to be on your PATH already, or the server will not start.
Wrote 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/skynetcmd/m3-memory/codex-memory)<a href="https://agentmods.dev/mcp/skynetcmd/m3-memory/codex-memory"><img src="https://agentmods.dev/badge/mcp/skynetcmd/m3-memory/codex-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/skynetcmd/m3-memory/codex-memory"><img src="https://agentmods.dev/badge/mcp/skynetcmd/m3-memory/codex-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
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 4d 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
{
"memory": {
"type": "stdio",
"command": "m3",
"args": [],
"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.
- 4d ago First seen · 8 lines scan A d0608f554b6b
memory is an MCP server published in the GitHub repository skynetcmd/m3-memory (29 stars, last pushed 4d 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-10-20.
Other mcp servers, from other repositories
inspeximus
MCP server "inspeximus", hosted remotely at pypi.org, as configured in DanceNitra/inspeximus. Needs 1 environment variable to run.
writing-context-rtfm
Context engine prioritizing RTFM search results into compact context packs. Runs locally from the writing-context-rtfm Python package.
gctrl
Governed graph-native agent memory: knowledge extraction, fusion, hybrid RAG, scoped access tokens. Runs locally from the gctrl-mcp npm package. Needs 3 environment variables to run.
cockroachdb-cloud
MCP server "cockroachdb-cloud", hosted remotely at cockroachlabs.cloud, as configured in vinayaksonthalia/obliviate.
obliviate
Add your description here. Runs locally from the mcp_server.py Python package.
cctx-optimizer
Reduce Claude Code token usage by 70-90% with cross-session memory and four-layer optimization: semantic codebase indexing, PostToolUse tool compression, turn summarization, and session consolidation. MCP server powered by Ollama — zero API calls, runs en. Runs locally from the cctx-optimizer npm package.