SearchCLI is a command-line interface for connecting agent or business systems to Volcengine’s search, recommendation, and conversational-retrieval services. It is for developers who need to onboard data, build and test retrieval workflows, adjust search strategies, inspect poor results, and verify changes. Its catalogue entries provide installable skills for operating these workflows.
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/SearchCLI --skill vs-searchgit clone --depth 1 https://github.com/volcengine/SearchCLIWrote 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/searchcli/vs-search)<a href="https://agentmods.dev/skills/volcengine/searchcli/vs-search"><img src="https://agentmods.dev/badge/skills/volcengine/searchcli/vs-search/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/searchcli/vs-search"><img src="https://agentmods.dev/badge/skills/volcengine/searchcli/vs-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00027 | $0.02288 |
| Opus 5.5 | $0.00011 | $0.00915 |
| Sonnet 5.5 | $0.00005 | $0.00458 |
| Haiku 4.5 | $0.00003 | $0.00229 |
Grade A, and why
vs-search 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Viking Search
When to Use
Use this skill for:
- search query verification
- search scene inspection and updates
- online result checks
- recall or ranking issue diagnosis
- separating persistent scene config from request-only runtime parameters
- fine-grained operations / serving-controls updates, including query-specific search rules
If the user wants automated batch evaluation or similarity tuning across many queries and strategies, use vs-search-tuning instead.
Version Check
Before starting this skill workflow, run vs version check --json. Continue only when status is up-to-date. If status is update-available, stop and tell the user to update the cloned vs repository, then run git pull --ff-only, bash ./scripts/install.sh, and bash ./scripts/install-skills.sh all --target auto --force (PowerShell: scripts/install.ps1 and scripts/install-skills.ps1). If the status is unknown, stop and report that the CLI version could not be verified.
Preconditions
- an
application-idis available - if you will edit a scene, you should preferably know the
scene-id - for fresh apps, be prepared for the runtime not to be ready yet
- the agent should treat the installed CLI behavior as authoritative when help text, skill text, and runtime behavior disagree
Scope
Before changing anything, decide whether the user wants:
- a persistent search strategy change
- a temporary runtime verification
- a readiness diagnosis for a failing app
This skill stays at the search workflow level. Do not embed low-level API field mappings, payload design, or enum interpretation here. When a concrete command needs exact parameters, first consult vs-product-qa and the matching API reference. For search scene update, the authoritative scene publish contract is vs-product-qa/references/api-references/control-plane/scene/PublishSearchSceneV2.md.
Commands
search run: send a production-style search requestsearch scene create/search scene list/search scene get: manage search scenessearch scene update: update scene configurationapp status/app diagnose: inspect readiness before blaming the query
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.
- 1mo ago Changed 0dd734c3aaaa
- 1mo ago Changed · +2 lines c849e615dfc2
- 1mo ago Changed · +14 lines 2081cf2eb6d6
- 1mo ago First seen · 89 lines · 27 tokens per session scan A 5d341e772fcc
vs-search is a skill published in the GitHub repository volcengine/SearchCLI (1,189 stars, last pushed 3d ago), licensed Apache-2.0. It adds 27 tokens to every session and 2,288 once invoked, about $0.0001 per session on Opus 5.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.
Other skills, from other repositories
sentry
Generated by Gutenberg. Use this skill to call the sentry API through the local sentry CLI.
youtube-content
YouTube Data API — search, video details, channel info, transcripts.
systematic-debugging
Methodical bug investigation and root cause analysis.
debugging
Systematic bug investigation process — reproduce, isolate, root cause, fix, verify.
repo-analyze
The map, not the contents. One call replaces the cold-start dance — file-tree exploration, finding entrypoints, reading every manifest, scanning README. Session mining showed 67 grep + 60 ls ops on a typical fresh-repo session, almost all of it answerable from one structured payload.
docker-management
Docker container lifecycle management, Dockerfile authoring, and debugging.