Borrowing it
Nothing to install: this file belongs to kaaustubh/project-memory-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kaaustubh/project-memory-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/kaaustubh/project-memory-mcpWrote 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/instructions/kaaustubh/project-memory-mcp/agents-md)<a href="https://agentmods.dev/instructions/kaaustubh/project-memory-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/kaaustubh/project-memory-mcp/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.
<a href="https://agentmods.dev/instructions/kaaustubh/project-memory-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/kaaustubh/project-memory-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.08468 | $0.08468 |
| Opus 5.5 | $0.03387 | $0.03387 |
| Sonnet 5.5 | $0.01694 | $0.01694 |
| Haiku 4.5 | $0.00847 | $0.00847 |
Grade B, and why
project-memory-mcp AGENTS.md scanned grade B with 1 finding 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 1mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- 2026-06-05 (v1.3.0): Shipped the previously-deferred guaranteed-capture Stop hook, but as a SEPARATE concern from the MCP server: it's a `hook` subcommand of index.js, registered via `install-hook` into `~/.claude/sett How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
project-memory-mcp — Agent Memory
This is the tool's own dev memory. It is auto-loaded when you open this repo in an editor, but it is NOT shipped to npm (the
fileswhitelist excludes it). Note: the server excludes itself from project discovery (.memory-serveris dotfile- and SKIP-filtered inindex.js), so this project won't appear inlist_projectsor an all-projectssearch_issues— it's first-class only via the editor auto-load here.
What this is
A small local MCP server that gives AI coding agents (Claude Code, Cursor, any MCP client) a shared, persistent memory of a folder of projects: what each project is, key decisions, and every bug/issue faced during development.
- npm:
@kaaustubh/project-memory-mcp· repo: github.com/kaaustubh/project-memory-mcp - All logic lives in a single file:
index.js(~210 lines).
Architecture (the core ideas)
- Protocol: MCP = JSON-RPC 2.0 over stdio. The client spawns this script as a
subprocess and exchanges newline-delimited JSON messages (
initialize→notifications/initialized→tools/list→tools/call). - Stateless: every tool reads/writes plain files on disk and returns; nothing is held in memory between calls. Consequence: multiple clients (and machines) sharing the same files share one memory. The filesystem is the source of truth.
- Two-layer memory (push vs pull):
- Push —
<project>/AGENTS.mdis auto-loaded into the model's context by the editor (viaCLAUDE.md→@AGENTS.md), NOT by this server. Low-volume, durable: identity, decisions, learnings. Keep lean. - Pull —
<project>/issues.jsonlis NOT auto-loaded; high-volume bug history fetched on demand viasearch_issues. Keeps always-loaded context small but searchable.
- Push —
- Discovery is the filesystem, not a registry (
listProjectDirs): scanROOTfor subdirs containingAGENTS.md. Can't drift.
Stack & layout
- Node.js ESM (
"type": "module"), Node >= 18. - Deps:
@modelcontextprotocol/sdk(high-levelMcpServer+StdioServerTransport),zod(tool input schemas). index.js— server + all 16 tools + theinstallsubcommand (gated onargv[2]).install.sh— install path for the from-source (git clone) install.README.md— public docs (this is what shows on npmjs.com).ROOT=PROJECT_MEMORY_ROOTenv, else parent dir of the script.
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.
- 1mo ago Changed · +3 lines · +480 tokens per session e4e7df60bd1c
- 1mo ago Changed · +3 lines · +557 tokens per session bd7c4a588b39
- 2mo ago First seen · 119 lines · 7,431 tokens per session scan B 8dabe21f6be4
project-memory-mcp AGENTS.md is an instructions file published in the GitHub repository kaaustubh/project-memory-mcp (1 stars, last pushed 8d ago), licensed MIT. It adds 8,468 tokens to every session, about $0.0339 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
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
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, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.