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/alibaizhanov/mengramWrote 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/plugins/alibaizhanov/mengram/marketplace)<a href="https://agentmods.dev/plugins/alibaizhanov/mengram/marketplace"><img src="https://agentmods.dev/badge/plugins/alibaizhanov/mengram/marketplace/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/plugins/alibaizhanov/mengram/marketplace"><img src="https://agentmods.dev/badge/plugins/alibaizhanov/mengram/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mengram marketplace 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 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.
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": "mengram",
"owner": {
"name": "Ali Baizhanov",
"email": "[email protected]",
"url": "https://mengram.io"
},
"plugins": [
{
"name": "mengram",
"version": "0.1.4",
"description": "Persistent memory for Claude Code that survives /clear, machine switches, and team handoffs. Hosted memory backend with hybrid retrieval (vector + BM25 + RRF), Ebbinghaus temporal decay, and importance weighting. Same memory available across Claude Code, Cursor, Codex, and ChatGPT.",
"source": {
"source": "git-subdir",
"url": "alibaizhanov/mengram",
"path": "integrations/claude-code-plugin"
},
"author": {
"name": "Ali Baizhanov",
"email": "[email protected]",
"url": "https://mengram.io"
},
"homepage": "https://mengram.io",
"license": "Apache-2.0",
"category": "productivity",
"keywords": [
"memory",
"mcp",
"context",
"cross-device",
"hybrid-retrieval",
"anthropic",
"persistence"
]
}
]
}The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
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 First seen · 37 lines scan A 959f5d7d7f7f
mengram marketplace is a plugin published in the GitHub repository alibaizhanov/mengram (204 stars, last pushed 29d 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
iai-memory
Persistent local memory for your assistant: every turn captured verbatim, relevant memory injected at session start and before each turn, and fourteen memory tools over MCP. Requires the iai-pme package (pip install iai-pme).
mnemoverse-memory
Persistent memory for AI agents, shared across tools: write a memory in one MCP client, recall it in another. OAuth sign-in, no API key to paste.
perenna
A lightweight, Git-backed permanent memory for AI agents.
inspeximus
Self-correcting memory for Claude Code. Facts you correct stay corrected, deletions leave a signed receipt you can verify offline, and storing something never calls a model. Also ships the checks: erasureresidue asks whether the bytes actually went — on any store, not just this one.
alice-memory
Local-first memory for Claude Code: an MCP server and a SessionStart brief on one SQLite file.
alicememory marketplace
Alice Memory plugins for Claude Code.