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.
/plugin marketplace add Coding-Dev-Tools/engraphisnpx agentmods add plugins/coding-dev-tools/engraphis/engraphisgit clone --depth 1 https://github.com/Coding-Dev-Tools/engraphisGrade A, and why
engraphis 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.
What it actually says
{
"name": "engraphis-memory",
"version": "1.6",
"description": "Give agents durable, scoped, explainable memory across sessions and repos via the Engraphis MCP tools. Use when you learn something worth keeping, need prior context before acting, or ask why/how a fact changed. Covers remember/recall, why/timeline, forget/pin/correct, sessions, and code search.",
"author": {
"name": "The Engraphis Authors",
"url": "https://github.com/Coding-Dev-Tools/engraphis"
},
"repository": "https://github.com/Coding-Dev-Tools/engraphis",
"license": "Apache-2.0",
"keywords": [
"engraphis",
"memory",
"mcp",
"agents",
"recall",
"bi-temporal",
"claude-code"
]
}
What ships with it
2 files beside plugin.json 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.
- 2d ago First seen · 21 lines scan A 94bfa06317a8
engraphis is a plugin published in the GitHub repository Coding-Dev-Tools/engraphis (170 stars, last pushed 2d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-30.
Other plugins, from other repositories
journal
Personal journaling system built on Binder — morning briefings, day planning, reflections, summaries, and period-level goal tracking.
talamus-memory
Durable, local-first agent memory with cited retrieval, provenance, history, and MCP tools.
agentmemory
Upstream-compatible AgentMemory plugin bundled with the independent Windows/Codex downstream. 12 hooks, 56 MCP tools, 8 skills, real-time viewer.
pax-memory
Official paxm integrations for Claude Code.
autograph
Schema-as-code memory engine for Obsidian vaults that AI agents write to: typed cards, entity dedup, link repair, update-in-place (supersede + History), Ebbinghaus decay, MOC generation, and a vault health score. Plain Markdown you own, Python stdlib only. Ships the autograph skill plus a /research slash command that…
tree-ring-memory
Local-first memory lifecycle, project bootstrap, and receipt-backed harness guidance for Claude Code using Tree Ring Memory v0.15+.