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-chatnpx skills add volcengine/SearchCLI --skill vs-chatgit 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.00022 | $0.00554 |
| Opus 5 | $0.00011 | $0.00277 |
| Sonnet 5 | $0.00004 | $0.00111 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
vs-chat 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 yesterday.
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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Viking Chat
When to Use
Use this skill for conversational search requests, session continuity, multi-turn checks, retrieval verification, and response inspection.
Preconditions
- an
application-idis available - the application is preferably already ready
Commands
chat run: send a conversational search request with full payload controlapp status/app diagnose: confirm readiness before testing chat behavior
Workflow
- Check
app statusfirst and confirm the application is ready - Use
chat runfor the first message - If you need multi-turn behavior, pass
session-idexplicitly - Use the full request payload when you need tighter control over the request
- If you request
--format json, parse one JSON document; do not treat the output as NDJSON - Summarize whether retrieval was triggered, whether relevant items were returned, and whether session continuity is preserved
Customer Environment Principle
- In customer environments, assume repository source code is unavailable.
- Execute tasks using only the installed skills, the packaged
vsCLI surface (--help, command output, and observed runtime behavior), and explicit user-provided information. - Do not rely on reading local repository source files, generated repo snapshots, or implementation details to decide runtime actions.
- If the installed CLI behavior conflicts with a skill, trust the installed CLI behavior first.
- If the skills and the packaged CLI still do not provide enough information to proceed safely, stop and ask the user instead of searching source code.
Constraints
- Before executing any concrete
vs ...command in this chat workflow, first consultvs-product-qato verify the current command surface, required flags, payload fields, input format, and allowed values. Only after that check may you finalize parameters and run the command. vs chat ...is the conversational search runtime surface- When debugging parsing issues, inspect the raw JSON response first instead of adding an extra line-oriented parser
- If a command failure or user follow-up turns into a product concept, capability, API field, console UI path, purchase, billing, or general troubleshooting question outside this chat workflow, temporarily hand off to
vs-product-qa; return to this workflow only after the grounded product answer is complete.
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.
- yesterday First seen · 50 lines · 22 tokens per session scan A 05588dc65a20
vs-chat is a skill published in the GitHub repository volcengine/SearchCLI (1,176 stars, last pushed 5d ago), licensed Apache-2.0. It adds 22 tokens to every session and 554 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'…
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.
zero-api-key-web-search
Codex-compatible skill for source-backed web search, page reading, and evidence-aware claim checking. Use it to verify factual answers with live results and explicit source handling. v23: multi-engine SERP (7 engines), Web Unlocker for blocked pages, auto-fallback on 403/429.