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/takaok5/codex-project-memoryInstalling this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
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/takaok5/codex-project-memory/project-memory)<a href="https://agentmods.dev/mcp/takaok5/codex-project-memory/project-memory"><img src="https://agentmods.dev/badge/mcp/takaok5/codex-project-memory/project-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/takaok5/codex-project-memory/project-memory"><img src="https://agentmods.dev/badge/mcp/takaok5/codex-project-memory/project-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
project-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 1mo 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
{
"project-memory": {
"command": "node",
"args": [
"scripts/bootstrap-mcp.mjs"
]
}
}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.
- 1mo ago First seen · 8 lines scan A d6e4aa14badf
project-memory is an MCP server published in the GitHub repository takaok5/codex-project-memory (0 stars, last pushed 2mo ago), licensed MIT. 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-31.
Other mcp servers, from other repositories
codex_native_memory
MCP server "codexnativememory" as configured in BulbuLbul86/codex-native-memory. Launched with powershell.exe -NoProfile -ExecutionPolicy Bypass -File ./scripts/run-mcp.ps1.
obsidian-hybrid-search
Search Obsidian vaults with hybrid full-text, fuzzy, semantic, and graph retrieval. Runs locally from the obsidian-hybrid-search npm package. Needs 10 environment variables to run.
vision-memory-mcp
MCP server "vision-memory-mcp" as configured in putervision/state-memory-mcp. Launched with vision-memory-mcp run. Needs 1 environment variable to run.
state-memory-mcp
MCP server "state-memory-mcp" as configured in putervision/state-memory-mcp. Launched with state-memory-mcp run.
mcp-memory-sqlite
SQLite-based persistent memory tool for MCP with text search. Runs locally from the mcp-memory-sqlite npm package.
rekindle
MCP session continuity engine. Boot reports, orientation scoring, and end-session capture. SQLite. Runs locally from the rekindle npm package.