What is memsum AGENTS.md?

Repository instructions for Mem·Sum, a communication and memory layer that organizes information around relationships and shared workspaces. Agents interpret messages and choose how to organize the resulting notes, while the server protects structure and records.

Use it when querying or changing a Mem·Sum vault, routing relationship-based messages, updating wiki pages, linking related information, or enriching stored resources.

It explains the rules for working with a Mem·Sum vault and helps preserve identities, links, timestamps, sources, and workspace boundaries. This reduces the risk of misrouting information or damaging the vault structure.

How docgotham/memsum configures Codex and OpenCode

Reuse

Borrowing it

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

Clone the repo

git clone --depth 1 https://github.com/docgotham/memsum

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/docgotham/memsum/agents-md/github.svg)](https://agentmods.dev/instructions/docgotham/memsum/agents-md)

Your own site

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

Per session 3,186 This file is loaded in full into every session.

When invoked 3,186 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.03186	$0.03186
Opus 5.5	$0.01274	$0.01274
Sonnet 5.5	$0.00637	$0.00637
Haiku 4.5	$0.00319	$0.00319

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

Security

Grade A, and why

memsum 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 · 175 lines

How it starts

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

AGENTS.md - Mem·Sum

This is the repository-level agent entry point for Mem·Sum.

For vault operations, the operational contract is DMSUM.md. Read it before changing or querying a Mem·Sum vault. In the local test, read the runtime vault copy through MCP:

read_file("DMSUM.md")

Core Orientation

Mem·Sum is an agent-native, relationship-scoped communication and memory layer. It is not the agent. A participant writes to their own agent, usually with +sum, +dm, or +dmsum, and the agent routes the act through the passive Mem·Sum layer.

Identity and routing can be global. Meaning is relational. In routed local mode, one MCP server may use .dmsum/registry.json to route across many relationship workspaces, but each workspace still has its own raw interactions, wiki updates, wiki graph, participants, and participant-specific preferences.

The server protects structure, provenance, IDs, timestamps, paths, coordination, and dry-run notifications. Agents provide the judgment: interpreting ordinary language, choosing target wiki pages, creating supporting wiki pages, enriching resources, linking the graph, and writing useful prose.

The current product direction: a hosted Supabase/Postgres graph exposed through a remote MCP/API on Vercel. Local filesystem and Git-sync work remain useful prototype, export, backup, and development infrastructure, but they are no longer the core product sync architecture.

Current State And Invariants (2026-07-13)

The product is live. The hosted MCP endpoint is https://sum.memsum.ai/mcp (the bare host https://sum.memsum.ai also serves MCP); the dashboard, site, and invite links are on https://memsum.ai. The legacy host dmsum-hosted-mvp.vercel.app keeps serving everything, so connectors registered against it continue to work. The kernel is open source (Apache-2.0) at https://github.com/docgotham/memsum, published as snapshots from a private operating archive.

Naming invariants — prose says Mem·Sum; these machine-facing names are frozen on purpose and must not be renamed in a cleanup:

Read the full file on GitHub · 175 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 · 175 lines · 3,186 tokens per session scan A 58ccdda9abe2

Subscribe to this mod's changes

memsum AGENTS.md is an instructions file published in the GitHub repository docgotham/memsum (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 3,186 tokens to every session, about $0.0127 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

memsum AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
memsum AGENTS.mddocgotham/memsum	Instructions file	0	2mo ago	Apache-2.0	A	3,186	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

memsum: Instructions file for Codex