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 vbcherepanov/total-agent-memorynpx agentmods add plugins/vbcherepanov/total-agent-memory/marketplacegit clone --depth 1 https://github.com/vbcherepanov/total-agent-memoryGrade A, and why
vbcherepanov 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 3d 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": "vbcherepanov",
"description": "Local-first tooling for AI coding agents.",
"owner": {
"name": "Vitalii Cherepanov",
"url": "https://github.com/vbcherepanov"
},
"plugins": [
{
"name": "total-agent-memory",
"displayName": "Total Agent Memory",
"description": "Persistent local memory: temporal knowledge graph, procedural memory, AST codebase ingest, cross-project analogy. 74 MCP tools, zero LLM calls in the hot path, nothing leaves the machine.",
"source": {
"source": "github",
"repo": "vbcherepanov/total-agent-memory"
},
"category": "Productivity",
"tags": ["memory", "mcp", "knowledge-graph", "local-first", "context"]
}
]
}
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 ships with it
1 file beside marketplace.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.
- 3d ago First seen · 22 lines scan A 8759a434a6cf
vbcherepanov marketplace is a plugin published in the GitHub repository vbcherepanov/total-agent-memory (66 stars, last pushed 6d 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-08-30.
Other plugins, from other repositories
task-orchestrator
Claude Code integration for MCP Task Orchestrator — schema-aware context, note-driven workflow.
longhand
Persistent local memory for Claude Code. Every tool call, every file edit, every thinking block from every session — stored verbatim on your machine. Semantic recall in 126ms with zero API calls.
awareness-memory
Persistent cross-session memory for Claude Code via Awareness Memory Cloud.
awareness-marketplace
Awareness Memory plugins marketplace for Claude Code.
claude-mneme
Automatic session memory for Claude Code — every session picks up where the last one left off.
claude-dejavu
Claude remembers its mistakes. Detects antipatterns from session logs and auto-patches CLAUDE.md.