agent-memory-mcp

agent-memory-mcp is a skill for Claude Code, Codex from bugrabilge/bilge-development-kit. It costs 26 tokens per session (554 once invoked), scanned A, a copy of agent-memory-mcp, MIT.

A persistent, searchable memory bank for AI agents that stores project architecture, patterns, and decisions. It runs as an MCP server, a service that gives an AI agent access to external tools and data.

In plain words
What is it for?
Use it to search stored project knowledge, record new decisions and patterns, and connect that memory to project documentation.
Why use it?
It lets agents retain project knowledge between conversations instead of starting with an empty memory each time.

Skill for Claude CodeCodex

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 skills/bugrabilge/bilge-development-kit/agent-memory-mcp
Any agent
npx skills add bugrabilge/bilge-development-kit --skill agent-memory-mcp
Clone the repo
git clone --depth 1 https://github.com/bugrabilge/bilge-development-kit

Made for: Claude Code, Codex.

Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 554 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 83% copy Near-identical to another mod 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.00026 $0.00554
Opus 5 $0.00013 $0.00277
Sonnet 5 $0.00005 $0.00111
Haiku 4.5 $0.00003 $0.00055

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

Security

Grade A, and why

agent-memory-mcp 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 3d 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.

Origin

This is a copy

83% identical to agent-memory-mcp — 7 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.

skills-extra/agent-memory-mcp/SKILL.md · 88 lines

How it starts

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

Agent Memory Skill

This skill provides a persistent, searchable memory bank that automatically syncs with project documentation. It runs as an MCP server to allow reading/writing/searching of long-term memories.

Prerequisites

  • Node.js (v18+)

Setup

  1. Clone the Repository: Clone the agentMemory project into your agent's workspace or a parallel directory:

    git clone https://github.com/webzler/agentMemory.git .agent/skills/agent-memory
    
  2. Install Dependencies:

    cd .agent/skills/agent-memory
    npm install
    npm run compile
    
  3. Start the MCP Server: Use the helper script to activate the memory bank for your current project:

    npm run start-server <project_id> <absolute_path_to_target_workspace>
    

    Example for current directory:

    npm run start-server my-project $(pwd)
    

Capabilities (MCP Tools)

memory_search

Search for memories by query, type, or tags.

  • Args: query (string), type? (string), tags? (string[])
  • Usage: "Find all authentication patterns" -> memory_search({ query: "authentication", type: "pattern" })

memory_write

Record new knowledge or decisions.

  • Args: key (string), type (string), content (string), tags? (string[])
  • Usage: "Save this architecture decision" -> memory_write({ key: "auth-v1", type: "decision", content: "..." })

memory_read

Retrieve specific memory content by key.

  • Args: key (string)
  • Usage: "Get the auth design" -> memory_read({ key: "auth-v1" })

memory_stats

View analytics on memory usage.

  • Usage: "Show memory statistics" -> memory_stats({})

Dashboard

This skill includes a standalone dashboard to visualize memory usage.

npm run start-dashboard <absolute_path_to_target_workspace>

Access at: http://localhost:3333

When to Use

This skill is applicable to execute the workflow or actions described in the overview.

Read the full file on GitHub · 88 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.

  1. 3d ago First seen · 88 lines · 26 tokens per session scan A 9fc0bf89b0a2

Subscribe to this mod's changes

agent-memory-mcp is a skill published in the GitHub repository bugrabilge/bilge-development-kit (10 stars, last pushed 4mo ago), licensed MIT. It adds 26 tokens to every session and 554 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to agent-memory-mcp, differing in 7 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens