What is openviking-controlplane?

A command-line tool for managing OpenViking collections, which are libraries of stored data, through a control-plane service. It also handles enterprise-library users and billing settings.

Use it to list, create, inspect, update, check usage for, or delete collections; retrieve a data-plane API key; manage library users; and configure billing.

It gives operators one interface for administering libraries and their access or billing configuration.

openviking-controlplane — Skill for Claude Code and Codex by volcengine: A command-line tool for managing OpenViking collections, which are…

Install

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.

agentmods

npx agentmods add skills/volcengine/mcp-server/openviking-controlplane

Any agent

npx skills add volcengine/mcp-server --skill openviking-controlplane

Clone the repo

git clone --depth 1 https://github.com/volcengine/mcp-server

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/volcengine/mcp-server/openviking-controlplane.svg)](https://agentmods.dev/skills/volcengine/mcp-server/openviking-controlplane)

Your own site

<a href="https://agentmods.dev/skills/volcengine/mcp-server/openviking-controlplane"><img src="https://agentmods.dev/badge/skills/volcengine/mcp-server/openviking-controlplane.svg" alt="Measured on agentmods" height="20"></a>

Per session 164 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,195 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00164	$0.02195
Opus 5	$0.00082	$0.01097
Sonnet 5	$0.00033	$0.00439
Haiku 4.5	$0.00016	$0.00219

Measured 4d ago against content hash 0b259a392cad, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

openviking-controlplane 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 4d 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.

server/mcp_server_openviking_controlplane/skills/openviking-controlplane/SKILL.md · 159 lines

How it starts

The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.

OpenViking Control Plane (`ov-cp`)

ov-cp is the CLI for the OpenViking control plane (topapi). It manages OV collections (libraries) and shares its core with the mcp-server-openviking-controlplane MCP server, so behavior is identical.

Setup

Install once (from the package dir): uv sync (or pip install -e .).

Configure via env vars (CLI flags -k / -e / --project override them):

Env var	Meaning	Default
`AGENTPLAN_API_KEY`	Ark AgentPlan ApiKey (sent as `Authorization: Bearer`)	— (required)
`VIKING_ENDPOINT`	Control-plane base URL	`https://api.vikingdb.cn-beijing.volces.com/openviking`
`OPENVIKING_PROJECT`	Default project	`default`
`VIKING_EXTRA_HEADERS`	Extra request headers, comma-separated `Key: Value`	—

export AGENTPLAN_API_KEY=ark-xxxxxxxx
# VIKING_ENDPOINT defaults to the public gateway — leave it unset for normal use.

The default endpoint is the reserved public gateway (not open yet). Override VIKING_ENDPOINT (or -e) only for testing — e.g. point it at a kubectl port-forward of the data-plane service. The full request URL is {endpoint}/api/openviking/{Action}.

Commands

ov-cp list                       # list collections (optionally --project X)
ov-cp get     <ResourceID>       # collection info (Status, models, version, ...)
ov-cp usage   <ResourceID>       # file counts / hourly CNY and AgentPlan AFP estimate
ov-cp api-key <ResourceID>       # default user's plaintext data-plane key
ov-cp api-key <ResourceID> --user-id xiaohong  # selected user's plaintext key
ov-cp create  --name my_kb       # create a collection (see below)
ov-cp update  <ResourceID> --description "..."   # update fields / switch billing
ov-cp update  <ResourceID> --model-api-key ark-xxx  # overwrite AgentPlan model key
ov-cp delete  <ResourceID> --yes # delete (irreversible; uninstalls the Helm release)

# users of an enterprise-tier library (key must be associated with the library):
ov-cp user list     <ResourceID>                     # users (ApiKey is masked)
ov-cp user list     <ResourceID> --role user --page 1 --limit 20
ov-cp user register <ResourceID> xiaohong            # new users always get role=user
ov-cp user update   <ResourceID> xiaohong --regenerate-key
ov-cp user delete   <ResourceID> xiaohong --yes      # revoke a user's credential

Read the full file on GitHub · 159 lines

Changes

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.

4d ago First seen · 159 lines · 164 tokens per session scan A 0b259a392cad

Subscribe to this mod's changes

openviking-controlplane is a skill published in the GitHub repository volcengine/mcp-server (321 stars, last pushed today), licensed MIT. It adds 164 tokens to every session and 2,195 once invoked, about $0.0008 per session on Opus 5. 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.

Backend and APIs

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens