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 agentmods add skills/volcengine/searchcli/vs-searchnpx skills add volcengine/SearchCLI --skill vs-searchgit clone --depth 1 https://github.com/volcengine/SearchCLIWhat 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.00027 | $0.01306 |
| Opus 5 | $0.00014 | $0.00653 |
| Sonnet 5 | $0.00005 | $0.00261 |
| Haiku 4.5 | $0.00003 | $0.00131 |
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 2d 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 — 89 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.
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.
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
Workflow
- Start by determining whether the user wants:
- a persistent search strategy change
- a temporary runtime verification
- a readiness diagnosis for a failing app
- If the request is a persistent search strategy change, use
search scene list/getfirst and inspect the current scene before mutating it. - Before running any concrete command, consult
vs-product-qato confirm the current command behavior and the exact parameter requirements. - Use
search runfor verification requests andsearch scene updatefor persistent scene changes. - After every scene mutation, immediately read the scene back with
search scene getand verify that the intended change is visible online. - If a fresh app fails, check
app statusand thenapp diagnose. - Only after readiness is clear should you focus on recall quality or scene configuration.
- If the command behavior conflicts with the skill text or
--help, trust the installed CLI behavior first, and only then inspect repository code when needed to explain or fix the gap.
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.
- 2d 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,175 stars, last pushed 6d ago), licensed Apache-2.0. It adds 27 tokens to every session and 1,306 once invoked, about $0.0001 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.
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…
linkly-ai
Search, browse, read, and take notes across the user's documents indexed by Linkly AI — local files and linked cloud libraries. Use when the user asks to 'search my documents', 'find files about a topic', 'read a local document', 'what's in this folder', 'list the files in that library', 'browse document outlines'…
youtube-content
YouTube Data API — search, video details, channel info, transcripts.
zero-api-key-web-search
OpenClaw skill for source-backed web search, page reading, and evidence-aware claim checking. No API keys required by default; optional providers can be enabled for stronger coverage. v23: multi-engine SERP (7 engines), Web Unlocker for blocked pages, auto-fallback on 403/429.
zero-api-key-web-search
Claude Code-compatible skill for source-backed web search, page reading, and evidence-aware claim checking. Use it when an answer depends on current facts, live sources, or explicit support/conflict handling. v23: multi-engine SERP (7 engines), Web Unlocker for blocked pages, auto-fallback on 403/429.