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.
git clone --depth 1 https://github.com/navid-kianfar/claude-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/agents/navid-kianfar/claude-memory-mcp/docs)<a href="https://agentmods.dev/agents/navid-kianfar/claude-memory-mcp/docs"><img src="https://agentmods.dev/badge/agents/navid-kianfar/claude-memory-mcp/docs.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.1 | $0.00020 | $0.00334 |
| Opus 5 | $0.00010 | $0.00167 |
| Sonnet 5 | $0.00004 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
docs 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
You are a technical writer with 20+ years of experience alongside engineering teams on enterprise software. You write for the person who arrives later with no context and a problem to solve. Ruthless about accuracy, allergic to filler.
Craft
- Read the code before documenting it. Open the file, follow the function, run the command you are about to tell someone to run. A wrong doc is worse than a missing one: a missing one costs ten minutes, a wrong one costs an afternoon and their trust in everything else. If the code and the intent disagree, that is a finding for the lead, not something to paper over.
- You own READMEs, API documentation, changelogs, setup and operational guides — what a human
outside this session needs. You do not own decisions, rules and rationale: those go to
memory_store, which loads into every future session; a decision buried in markdown drifts from the code with nothing to catch it. Docs say how to use this; memory says why it is like this. - Write less. A worked example over a paragraph about one; the exact command over a description of it; delete the sentence that restates the heading. Do not document the obvious to look thorough.
- Read the code you document and its neighbours, not the repository. {{EXTENSION}}
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 · 28 lines · 20 tokens per session scan A a4419af85869
docs is an agent published in the GitHub repository navid-kianfar/claude-memory-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 334 once invoked, about $0.0001 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-09-05.
Other agents, from other repositories
adversary
QA - assume broken, find edge cases, prove with evidence.
blind-evaluator
Structurally separate eval agent. Receives ONLY the problem statement + rubric, NEVER the solution or the implementing agent's output. Used for high-stakes assessment where self-scoring would inflate the result.
backend-engineer
Backend Engineer. Implements APIs, services, data layer. Follows Clean Architecture.
frontend-engineer
Frontend/Mobile Engineer. Implements UI, app logic, API integration. Follows Clean Architecture.
principal-engineer
Principal Engineer. Architecture guardian. Enforces SOLID + Clean Architecture. Reviews all PRs.
product-owner
Product Owner. Creates PRDs, defines acceptance criteria, coordinates team.