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.
npx skills add volcengine/OpenViking --skill ov-memory-doctorgit 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/skills/volcengine/openviking/ov-memory-doctor)<a href="https://agentmods.dev/skills/volcengine/openviking/ov-memory-doctor"><img src="https://agentmods.dev/badge/skills/volcengine/openviking/ov-memory-doctor/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/skills/volcengine/openviking/ov-memory-doctor"><img src="https://agentmods.dev/badge/skills/volcengine/openviking/ov-memory-doctor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00181 | $0.04402 |
| Opus 5.5 | $0.00072 | $0.01761 |
| Sonnet 5.5 | $0.00036 | $0.00880 |
| Haiku 4.5 | $0.00018 | $0.00440 |
Grade E, and why
ov-memory-doctor scanned grade E with 4 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 15d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
| `plugin disabled — every hook exits immediately` | No parseable config, `OPENVIKING_MEMORY_ENABLED=0`, or `claude_code.enabled: false` in ov.conf | Fix the reason it names. Fresh machine: create `~/.openviking/ovcli.co Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
| `not registered in installed_plugins.json` / `claude plugin list does not show …` | Plugin never installed, or installed under an old id | Re-run the one-line installer (`curl -fsSL https://openviking.ai/install \| bas Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
| `plugin is disabled in ~/.claude/settings.json` | Installed but `enabledPlugins` is false/missing | `claude plugin enable openviking-memory@openviking`, restart Claude Code. | Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| `not registered in installed_plugins.json` / `claude plugin list does not show …` | Plugin never installed, or installed under an old id | Re-run the one-line installer (`curl -fsSL https://openviking.ai/install \| bas 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 ships with it
1 file beside SKILL.md 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.
- 15d ago Changed · +1 lines scan C → E 5c60b4f12307
- 24d ago Changed · +3 lines 92b863e61116
- 27d ago Changed c231afcfb78b
- 1mo ago Changed · -3 lines 54bf2ee1c7cf
- 1mo ago Changed · -5 lines · -74 tokens per session 1feffd3fb390
- 1mo ago First seen · 211 lines · 255 tokens per session scan C 8731b90119ea
ov-memory-doctor is a skill published in the GitHub repository volcengine/OpenViking (40,015 stars, last pushed today), licensed AGPL-3.0. It adds 181 tokens to every session and 4,402 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it E with 4 findings (asks for root, downloads and executes remote code, reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
wiki
Decision-sensitive repository knowledge retrieval, authoring, maintenance, and trust audits using wiki-manager when available or an explicit local-file fallback. Use when repository knowledge could change a non-trivial decision or when the user mentions wiki, knowledge base, packets, schema reports, or wiki tools.
honcho-cli
Inspect and debug Honcho workspaces via the honcho CLI. Use when investigating peer representations, memory state, session context, or dialectic quality — any task that requires introspection of a Honcho deployment, including verifying that a recall/record memory loop is actually working.
causal-memory
Causal memory for agents — install/setup the causal-memory MCP server, then record decisions/outcomes and recall them before acting. Trigger when the user asks to install or set up causal-memory/agent memory, when causal-memory MCP tools are available and the agent faces a non-trivial decision (architecture, debugging…
gsd-forensics
Post-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong.
upload-debug-memory
Use after resolving a bug, test failure, build failure, CI issue, deployment issue, or framework/API pitfall when the verified lesson should be published to Noosphere for future agents.
gsd-resume-work
Resume work from previous session with full context restoration.