What is memory-mcp AGENTS.md?

Project instructions for using a persistent memory server, which stores information that can be retrieved in later coding sessions.

They are for deciding when to read or save project memories and how to connect to the local memory service.

They reduce the need to repeat project decisions, patterns, references, and user preferences after a session ends.

How joshdougall/memory-mcp configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to joshdougall/memory-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/joshdougall/memory-mcp/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/joshdougall/memory-mcp

Made for: Codex, OpenCode.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/joshdougall/memory-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/joshdougall/memory-mcp/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/joshdougall/memory-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/joshdougall/memory-mcp/agents-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/joshdougall/memory-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/joshdougall/memory-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,040 This file is loaded in full into every session.

When invoked 1,040 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.01040	$0.01040
Opus 5.5	$0.00416	$0.00416
Sonnet 5.5	$0.00208	$0.00208
Haiku 4.5	$0.00104	$0.00104

Measured 2mo ago against content hash 64388830a9d7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

memory-mcp AGENTS.md 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 2mo 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.

AGENTS.md · 112 lines

How it starts

The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Memory Instructions

A persistent memory MCP server is running and available to you. Use it to store and retrieve knowledge that should survive across sessions — decisions, patterns, references, and feedback that would otherwise be lost when the conversation ends.

Connection

Endpoint: http://127.0.0.1:3106/mcp (MCP over HTTP, Streamable HTTP transport)
Auth: If MEMORY_MCP_AUTH_TOKEN was set, include Authorization: Bearer <token> in requests. Check with the user if unsure.

When to read

At the start of each session, search for memories relevant to the current project or task before asking the user to re-explain context:

memory_search(tags=["your-project-name"])

When to write

Write when you discover something that should be remembered across sessions:

A pattern or convention the user corrected you on
An architectural decision and its rationale
A reference to an external resource or tool
A recurring preference or feedback
A project-level fact (deadline, constraint, stakeholder)

Do not write:

Ephemeral task state (use a STATE.md file for that)
Code patterns obvious from reading the repo
Anything already documented in project files

Memory types

Type	Use for
`pattern`	Recurring conventions, idioms, or approaches
`decision`	Architectural or technical choices with rationale
`reference`	Pointers to external resources, docs, or tools
`feedback`	How the user wants you to behave or approach work
`incident`	Post-mortems and lessons from failures
`project`	Project-level facts (team, deadlines, constraints)
`entity`	Named things (people, systems, accounts)
`state`	Short-lived state that spans a few sessions

Available tools

Tool	Description
`memory_search`	Filter by tags (intersection), type, project, or text
`memory_get`	Fetch one entry by ID — increments hit counter
`memory_set`	Create or update an entry — versioned on every write, optional compare-and-set
`memory_list`	List entries with optional type/project filter
`memory_delete`	Delete an entry (tombstone version written first)
`memory_history`	View version history for an entry
`memory_rollback`	Restore an entry to a previous version
`memory_prune_candidates`	Surface zero-hit stale entries for review (read-only)

Read the full file on GitHub · 112 lines

Changes

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.

2mo ago First seen · 112 lines · 1,040 tokens per session scan A 64388830a9d7

Subscribe to this mod's changes

memory-mcp AGENTS.md is an instructions file published in the GitHub repository joshdougall/memory-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 1,040 tokens to every session, about $0.0042 per session on Opus 5.5. 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.

Memory and context

memory-mcp AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
memory-mcp AGENTS.mdjoshdougall/memory-mcp	Instructions file	2	1mo ago	MIT	A	1,040	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

memory-mcp: Instructions file for Codex