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 skills/m-t-d-n/agentmemory-codex-windows/agentmemory-confignpx skills add M-T-D-N/agentmemory-codex-windows --skill agentmemory-configgit clone --depth 1 https://github.com/M-T-D-N/agentmemory-codex-windowsWrote 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/skills/m-t-d-n/agentmemory-codex-windows/agentmemory-config)<a href="https://agentmods.dev/skills/m-t-d-n/agentmemory-codex-windows/agentmemory-config"><img src="https://agentmods.dev/badge/skills/m-t-d-n/agentmemory-codex-windows/agentmemory-config.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00044 | $0.00387 |
| Opus 5 | $0.00022 | $0.00193 |
| Sonnet 5 | $0.00009 | $0.00077 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
agentmemory-config 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 4d 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.
This is a copy
100% identical to agentmemory-config — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
agentmemory reads configuration from the environment and from ~/.agentmemory/.env (one KEY=value per line, no export prefix). Restart the server after changing it.
Quick start
Enable richer memory and set a provider key in ~/.agentmemory/.env:
ANTHROPIC_API_KEY=sk-ant-...
AGENTMEMORY_AUTO_COMPRESS=true
AGENTMEMORY_INJECT_CONTEXT=true
Defaults worth knowing
- No API key is required. Without one, agentmemory runs zero-LLM with BM25 plus local embeddings.
- Token-spending features ship OFF on purpose:
AGENTMEMORY_AUTO_COMPRESS(LLM summaries) andAGENTMEMORY_INJECT_CONTEXT(auto context injection) both cost tokens proportional to tool-use frequency. - Tool visibility:
AGENTMEMORY_TOOLS=all(default) orcorefor the lean set. - Auth: set
AGENTMEMORY_SECRETto requireAuthorization: Beareron the REST API.
Ports
REST is the anchor at 3111. Streams = N+1 (3112), viewer = N+2 (3113), engine = N+46023 (49134). Relocate the whole block with --port <N> or --instance <N>.
See also
- agentmemory-rest-api for how the secret is used.
- agentmemory-architecture for the port quartet rationale.
Reference
The full recognized-variable list lives in REFERENCE.md, generated by scanning src/.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 38 lines · 44 tokens per session scan A 14fce9b1675c
agentmemory-config is a skill published in the GitHub repository M-T-D-N/agentmemory-codex-windows (2 stars, last pushed 4d ago), licensed Apache-2.0. It adds 44 tokens to every session and 387 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to agentmemory-config, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
engraphis-memory
Give the agent durable, scoped, explainable memory across sessions and repositories through the Engraphis MCP tools. Use when you learn a convention, decision, bug cause/fix, or user preference worth keeping; when prior context would help before you answer or act (to avoid re-asking or re-deriving); when asked "why is…
talamus-memory
Set up and use Talamus as durable, local-first memory for AI agents. Use when an agent needs to initialize or diagnose a Talamus brain, ingest files or repositories, retrieve cited context across sessions, inspect note history, verify memory against sources, review proposed corrections, connect Talamus through MCP, or…
shodh-memory
Persistent memory system for AI agents. Use this skill to remember context across conversations, recall relevant information, and build long-term knowledge. Activate when you need to store decisions, learnings, errors, or context that should persist beyond the current session.
plur-memory
Persistent learning for AI agents. Open engram format. Your agent learns from corrections, remembers across sessions, and transfers knowledge across domains.
lemmalog
Externalize working memory and logical state into the lemmalog Datalog engine (MCP). Use for ANY multi-step task where state should outlive one context window or span agents: long investigations, debugging sessions, audits, multi-agent searches, systematic explorations, planning with many interdependent constraints…
ori-memory
Persistent agent memory with learning retrieval. Knowledge graph on markdown files — capture insights, decisions, research, and learnings during work, then retrieve them weeks or months later. Use when knowledge is too valuable to lose but too much to inject into every prompt.