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/studiomeyer-io/studiomeyer-marketplaceWrote 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/studiomeyer-io/studiomeyer-marketplace/studiomeyer-memory-chat)<a href="https://agentmods.dev/plugins/studiomeyer-io/studiomeyer-marketplace/studiomeyer-memory-chat"><img src="https://agentmods.dev/badge/plugins/studiomeyer-io/studiomeyer-marketplace/studiomeyer-memory-chat/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/studiomeyer-io/studiomeyer-marketplace/studiomeyer-memory-chat"><img src="https://agentmods.dev/badge/plugins/studiomeyer-io/studiomeyer-marketplace/studiomeyer-memory-chat.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
studiomeyer-memory-chat 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": "studiomeyer-memory-chat",
"displayName": "StudioMeyer Memory",
"version": "0.2.0",
"description": "Use all 56 StudioMeyer Memory tools through your own OAuth account, with guided skills for sessions, recall, decisions, knowledge graph, proactive suggestions, and careful maintenance.",
"author": {
"name": "StudioMeyer",
"email": "[email protected]",
"url": "https://studiomeyer.io"
},
"homepage": "https://studiomeyer.io/en/services/memory",
"repository": "https://github.com/studiomeyer-io/studiomeyer-marketplace",
"privacyPolicyUrl": "https://studiomeyer.io/en/privacy",
"supportUrl": "https://studiomeyer.io/en/contact",
"termsOfServiceUrl": "https://studiomeyer.io/en/terms",
"documentationUrl": "https://github.com/studiomeyer-io/studiomeyer-marketplace/blob/main/plugins/studiomeyer-memory-chat/README.md",
"license": "MIT",
"keywords": [
"memory",
"knowledge-graph",
"productivity",
"mcp"
]
}
What it installs
The manifest is a name and a version. 4 skills travel with it, and installing the plugin installs all of them — 122 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 Changed · +4 lines 28382884fcf2
- 4d ago First seen · 21 lines scan A 6870ca1c957e
studiomeyer-memory-chat is a plugin published in the GitHub repository studiomeyer-io/studiomeyer-marketplace (2 stars, last pushed 2d ago), licensed MIT. 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-10-12.
Other plugins, from other repositories
7xuanlu-wenlan marketplace
Plugin marketplace listing 1 plugin: wenlan.
total-agent-memory
Persistent local memory for Claude Code — temporal knowledge graph, procedural memory, AST codebase ingest, cross-project analogy. Installs the MCP server, the memory-protocol skill and the capture hooks in one step.
claude-code-hermit
Your own local Claude Tag, in the Claude app, Discord, Telegram, or a custom Claude Code channel.
engram
Durable, local-first graph memory for AI coding assistants: decisions with reasons, gotchas, conflicts — inspectable and editable in a graph pane.
scout
Autonomous knowledge management and daily briefing system. Monitors your work tools (Slack, Calendar, Linear, GitHub, etc.), synthesizes findings into a persistent knowledge base with a formal ontology, and delivers daily action items — all running unattended via scheduled Claude Code sessions. Six session types…
second-brain
Agentic workflow with memory and tribal knowledge. Transforms Claude from goldfish to elephant with persistent knowledge across sessions.