dev-memory-manager

A manager for development knowledge stored in an LLM Memory MCP server, a service that lets an AI retain useful project context. It focuses on preserving important code patterns, discoveries, and technical decisions during development sessions.

In plain words
What is it for?
Use it to capture development insights, preserve implementation decisions, and manage important project context before a session is compacted.
Why use it?
It helps prevent critical context from being lost as a conversation grows or is shortened. This makes earlier project knowledge easier to retain and reuse.

Agent

Install

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.

agentmods
npx agentmods add agents/andreahaku/llm_memory_mcp/dev-memory-manager
Clone the repo
git clone --depth 1 https://github.com/andreahaku/llm_memory_mcp
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,090 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.03090
Opus 5 $0.00000 $0.01545
Sonnet 5 $0.00000 $0.00618
Haiku 4.5 $0.00000 $0.00309

Measured 2d ago against content hash 4a85f75792b5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

dev-memory-manager 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 2d 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/dev-memory-manager.md · 331 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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.

  1. 2d ago First seen · 331 lines · 0 tokens per session scan A 4a85f75792b5

Subscribe to this mod's changes

dev-memory-manager is an agent published in the GitHub repository andreahaku/llm_memory_mcp (4 stars, last pushed 6mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 3,090 tokens. 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.