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.
npx agentmods add instructions/jryom/agentsmd-memory/agents-mdgit clone --depth 1 https://github.com/jryom/agentsmd-memoryWhat 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 | $0.00358 | $0.00358 |
| Opus 5 | $0.00179 | $0.00179 |
| Sonnet 5 | $0.00072 | $0.00072 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
agentsmd-memory 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 yesterday.
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
agentsmd-memory
Zero-dependency MCP server exposing memory_save/memory_forget. Tools never write files; they return merge instructions the agent applies itself. Ships opencode, Claude Code, and Codex integrations, all injecting a per-turn nudge (shared resolveNudge in src/plugin.mjs, overridable via MEMORY_NUDGE).
Resolution
- File resolution (unset
MEMORY_FILE) prefersAGENTS.md, falls back toCLAUDE.md; nearest-up wins,AGENTS.mdbeatsCLAUDE.mdat the same level, andAGENTS.mdis created when nothing exists.MEMORY_FILEset = single explicit name, no fallback. memoryFileNames()returns the ordered candidate list;memoryFileName()kept as[0]for back-compat.resolveMemoryFileaccepts a name or an array.
Gotchas
- Claude Code auto-discovers
hooks/hooks.json; do NOT list it underhooksin.claude-plugin/plugin.json— causes a "Duplicate hooks file" load failure. - Codex also auto-discovers
hooks/hooks.json; keep the shared hook command as one string. Codex ignores Claude-style separateargsin hook handlers. - Claude Code and Codex share
.mcp.json, which launches unpinnednpx -y agentsmd-memory. This intentionally follows npm'slatesttag; plugin-root variables are hook-only in Codex and cannot portably locate the bundled MCP source across both clients. marketplace.jsonrejects a$schemakey and wants the description undermetadata.description(not top-level).
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.
- yesterday First seen · 19 lines · 358 tokens per session scan A d0513e613f64
agentsmd-memory AGENTS.md is an instructions file published in the GitHub repository jryom/agentsmd-memory (1 stars, last pushed 22d ago), licensed MIT. It adds 358 tokens to every session, about $0.0018 per session on Opus 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.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.