OpenViking is an open-source context database for AI agents that stores memories, resources, and skills in a browsable virtual filesystem. Agents use it to find and load relevant context in layers while inspecting how retrieval decisions were made.
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/volcengine/OpenVikingWrote 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/volcengine/openviking/cursor-memory-plugin)<a href="https://agentmods.dev/plugins/volcengine/openviking/cursor-memory-plugin"><img src="https://agentmods.dev/badge/plugins/volcengine/openviking/cursor-memory-plugin.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
openviking-memory 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 today.
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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- today First seen · 21 lines scan A 1d052e8dd457
openviking-memory is a plugin published in the GitHub repository volcengine/OpenViking (35,832 stars, last pushed today), licensed AGPL-3.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-09-07.
Other plugins, from other repositories
causal-memory
Persistent causal memory for Claude Code — decisions, outcomes, and lessons that survive compaction. Same-context counterfactuals (natural experiments), a falsifiable prediction ledger, and an activation skill that teaches when to recall and record.
l123-harness
A project structure for keeping an AI agent’s memory outside the model in three layers: persistent notes, an index, and detailed records. It also provides templates, approval controls, event logs, context-saving procedures, and weekly review tools.
deja
deja-vu memory for Gemini CLI: the coding sessions already on your disk — Gemini CLI, Claude Code, Codex, Cursor and eighteen more — searchable and recalled, including work from before it was installed.
engraphis-memory
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.
emem
Shared, verifiable memory for AI agents. Two layers, one trust surface. Earth-scale fact substrate: every patch of ground gets a 64-bit address (cell64, about 9.55 m), and every measurement at that cell is a signed fact keyed by (cell, band, tslot), ed25519-signed by the responder over the blake3 of its canonical CBOR.
knowl
Persistent memory for Claude Code. Facts are typed, sourced, and retired when they change, so a query returns the current answer rather than every answer it has ever held. Local SQLite in your repository — no API key, nothing uploaded.