openviking-token-saver
ReviewAudited by ClawScan on May 10, 2026.
Overview
This looks like a legitimate OpenViking context/search skill, but it deserves review because it can recursively ingest local files into persistent memory and uses provider API keys without clear scoping or exclusion controls.
Install only if you want OpenViking to maintain a persistent local context database. Before using it, review the shell scripts, use a limited provider API key, add only specific non-sensitive folders, avoid secrets and broad home/project roots, and stop optional background services when not needed.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If pointed at a broad project or home directory, private code, configs, or secrets could be stored in the context database and reused in later agent tasks.
A directory add recursively ingests every matching file into OpenViking. The artifacts do not show exclusions for secrets, .git, dependency folders, retention limits, or per-file approval.
pattern = os.path.join(target, "**", "*.*"); files = glob.glob(pattern, recursive=True) ... client.add_resource(path=f)
Only add narrowly scoped folders, avoid home/root directories, exclude secrets and generated/vendor folders, and document how indexed data can be reviewed and deleted.
The configured provider key may authorize model/embedding calls and incur costs; it is stored locally in ~/.openviking/ov.conf.
The setup script prompts for a model-provider API key and writes it into the OpenViking configuration file.
prompt "API Key: " read -rs API_KEY ... "api_key": "$API_KEY"
Use a restricted key where possible, protect ~/.openviking/ov.conf, rotate the key if exposed, and ensure the registry metadata clearly declares this credential need.
Install behavior depends on current upstream PyPI/GitHub content, so a compromised or changed upstream release could affect the local environment.
The installer pulls the latest unpinned OpenViking package and optionally executes a remote GitHub install script.
$VENV_PIP install openviking --upgrade --force-reinstall ... curl -fsSL https://raw.githubusercontent.com/volcengine/OpenViking/main/crates/ov_cli/install.sh | bash
Prefer pinned versions or checksums, inspect remote install scripts before running them, and install from trusted releases.
Local OpenViking services may keep running after setup and continue exposing a local API/Web UI on the machine.
The skill documents optional background API/Web UI services. They are disclosed and localhost-oriented, but they persist until stopped.
nohup ~/.openviking/venv/bin/openviking-server > ~/.openviking/server.log 2>&1 &
Start the server only when needed, keep it bound to localhost, review logs, and stop the processes when finished.