What is memory-mcp AGENTS.md?

Repository instructions for coding agents working on jommar/memory-mcp. They point agents to the project’s design, setup, tool, and reliability documents and state additional rules for keeping them current.

Use them when modifying this repository, especially when changing features, commands, paths, design decisions, or the user interface. They also specify the checks used for verification.

They reduce the risk of changing code without reading the project’s authoritative documentation or leaving instructions out of date.

How jommar/memory-mcp configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to jommar/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/jommar/memory-mcp/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/jommar/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/jommar/memory-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/jommar/memory-mcp/agents-md)

Your own site

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

Per session 625 This file is loaded in full into every session.

When invoked 625 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.00625	$0.00625
Opus 5.5	$0.00250	$0.00250
Sonnet 5.5	$0.00125	$0.00125
Haiku 4.5	$0.00063	$0.00063

Measured 2mo ago against content hash b6b951a19ab4, 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 · 41 lines

How it starts

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

AGENTS.md

Guidance for AI coding agents. This file only points at the real docs and lists rules not stated elsewhere — read the linked files before working here.

Read first

Doc	Covers
DESIGN.md	Authoritative design: architecture, data model, reliability engine, tool surface, stack pins (§3), repo layout (§7), session learnings (§11)
README.md	Install/run, `MEMORY_*` env config, maintenance CLI, explorer UI
docs/tools.md	Reference for all 10 MCP tools
docs/reliability.md	Reliability formula, decay λ/tiers, lifecycle rules behind `consolidate`

Rules

Keep DESIGN.md current. Update it in the same change set when you ship or change a feature — new behavior, replaced decisions, corrected stack/version facts. Stale design = bug.
Keep this file current too. If your change invalidates any command, path, or claim here, update or delete that line in the same change set — a stale instruction is worse than none.
Verify like CI does (.github/workflows/ci.yml, Node 22 + 24): npm run lint && npm run typecheck && npm test; when ui/ is touched also npm run ui:typecheck && npm run ui:build && npm run ui:test.
Orchestrator sessions live under .orchestrator/<NN-slug>/ (gitignored). Never edit or reuse a past session's directory; number new ones (01-, 02-, …) so ls orders them.
Node ≥22, TypeScript ESM (nodenext: relative imports end in .js; verbatimModuleSyntax requires import type). Stack pins live in package.json; decisions in DESIGN.md §2–3.

Tooling gotchas

There is no eslint/prettier/biome by design — npm run lint is tsc-based dead-code checking (--noUnusedLocals --noUnusedParameters --noUncheckedSideEffectImports). Don't add a linter or reformat the tree unasked.
npm test is not purely unit tests: test/packaging.test.ts runs npm run build, packs the tarball, installs it into a temp dir, and drives the compiled bins (dist/cli.js, dist/src/index.js) over stdio. While iterating, run one file: npx vitest run test/core/recall.test.ts (same pattern under ui/).
The suite is offline-safe: tests inject fake embedding providers; the only real-model test (test/embeddings/local.test.ts) skips itself unless .cache/models/ exists.

Read the full file on GitHub · 41 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 · 41 lines · 625 tokens per session scan A b6b951a19ab4

Subscribe to this mod's changes

memory-mcp AGENTS.md is an instructions file published in the GitHub repository jommar/memory-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 625 tokens to every session, about $0.0025 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-mcp AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
memory-mcp AGENTS.mdjommar/memory-mcp	Instructions file	0	2mo ago	MIT	A	625	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