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-recommendgit 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-recommend)<a href="https://agentmods.dev/skills/volcengine/searchcli/vs-recommend"><img src="https://agentmods.dev/badge/skills/volcengine/searchcli/vs-recommend/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-recommend"><img src="https://agentmods.dev/badge/skills/volcengine/searchcli/vs-recommend.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.00029 | $0.04273 |
| Opus 5.5 | $0.00012 | $0.01709 |
| Sonnet 5.5 | $0.00006 | $0.00855 |
| Haiku 4.5 | $0.00003 | $0.00427 |
Grade A, and why
vs-recommend 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 28d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Viking Recommend
When to Use
Use this skill for:
- recommendation runtime checks
- V2 recommend scene inspection, creation, publishing, deletion, and deployment verification
- V2 recommend rule inspection and management
- diagnosing whether bad recommendation results come from scene config, behavior-scene binding, user context, parent/item context, data readiness, or online config propagation
- separating persistent scene defaults from request-only runtime parameters
If the user asks a general product/API/auth/pricing question rather than a recommend workflow action, temporarily hand off to vs-product-qa and return here only after the grounded product answer is complete.
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 - runtime checks need a
scene-idand usually at least one ofuser-id,parent-id, or shopping-cart item context - scene creation needs an item dataset bound to the application and at least one behavior scene value from the bound UserEvent dataset; when the value is not explicit, resolve it with
vs dataset get --id <user-event-dataset-id> --fullfrom the UserEvent schema field whose business attribute is UserEventScene - if the scene does not exist yet, inspect the existing scene list first and only create a new scene when reuse is not possible
- 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:
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.
- 28d ago Changed · +1 lines 3b358f295cd1
- 1mo ago Changed · +108 lines · +4 tokens per session 2d0538dc2ff0
- 1mo ago First seen · 57 lines · 25 tokens per session scan A 25ded412c7cd
vs-recommend is a skill published in the GitHub repository volcengine/SearchCLI (1,189 stars, last pushed yesterday), licensed Apache-2.0. It adds 29 tokens to every session and 4,273 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
xerj-code
Reference-coding with XERJ. Clone the libraries that already solved your problem, index them locally, and retrieve the exact implementation before writing code — so the agent reads passages instead of re-deriving algorithms across retry loops. Use when starting a task in an unfamiliar API, porting an algorithm, or…
xerj-security-audit
Coverage-guaranteed whitebox security audit of a codebase using XERJ + tree-sitter AST. Use when the user wants to security-review PHP (or other-language) code with a provable "we enumerated every dangerous call" guarantee, or asks to run the WordPress-style sink census / audit. Drives an index-once, query-read-reason…
microsoft-build
Your companion for Microsoft Build 2026. Helps you find sessions relevant to your project, discover what's new for your tech stack, scaffold projects from sessions, and plan your event schedule. Activate when users mention sessions, schedule, what's new, Build, Ignite, AI Tour, Microsoft event, conference, or…
zens-ink
Free SEO toolkit for indie builders. 22 zero-dependency Python tools covering the full SEO workflow: keyword discovery (Google Autocomplete), keyword clustering (semantic grouping), keyword difficulty (SERP structure analysis, no Ahrefs needed), KGR opportunity scoring, search volume (Bing + Brave), real Ahrefs Domain…
geo-readiness
Make a site citable by AI engines (ChatGPT, Perplexity, Google AI Overviews) — Generative Engine Optimization. Audits robots.txt AI-crawler policy and the llms.txt layer, generates llms.txt / llms-full.txt from a static build or sitemap, and plans Query Fan-out content (the sub-queries AI engines spawn from a seed…
keyword-research
Find low-competition keyword opportunities without paid tools (Ahrefs, Semrush). Runs real zero-dependency Python CLIs: Google Autocomplete discovery (with a-z long-tail expansion), semantic clustering, Bing volume lookup, and automated KGR opportunity scoring. Use when the user wants keyword ideas for a niche, asks…