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-search-tuning-specify-policy-directiongit 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-tuning-specify-policy-direction)<a href="https://agentmods.dev/skills/volcengine/searchcli/vs-search-tuning-specify-policy-direction"><img src="https://agentmods.dev/badge/skills/volcengine/searchcli/vs-search-tuning-specify-policy-direction/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-tuning-specify-policy-direction"><img src="https://agentmods.dev/badge/skills/volcengine/searchcli/vs-search-tuning-specify-policy-direction.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 124 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00093 | $0.05410 |
| Opus 5 | $0.00046 | $0.02705 |
| Sonnet 5 | $0.00019 | $0.01082 |
| Haiku 4.5 | $0.00009 | $0.00541 |
Grade A, and why
vs-search-tuning-specify-policy-direction 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 today.
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 — 454 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Viking Search Tuning for Specified Policy Directions (vs-search-tuning-specify-policy-direction)
When to Use
Use this Skill when the user provides specific queries or a type of query, and explicitly specifies an "optimization policy direction" such as boosting the weight of a product type, increasing exposure for seasonal products, or fixing a class of bad cases.
Difference from global vs-search-tuning:
- This Skill does not modify primary recall parameters.
- This Skill does not create, modify, or derive scenes.
- This Skill validates and recommends strategies only through request-parameter passthrough, within the scope of the 8 business intervention methods.
- It is suitable for small-scale targeted tuning with a clear direction; it is not suitable for global similarity-recall strategy search.
Mode selection:
- If the user provides specific queries or bad cases: use Mode A.
- If the user only provides a policy direction and no specific queries: use Mode B. The Agent synthesizes 50 dataset-related queries.
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
- A Viking Search application id is available.
- A dataset id and baseline search scene id are either provided by the user or can be resolved from read-only CLI checks.
- The user has provided either concrete queries, a query type, or an explicit business policy direction.
vs auth status --jsonsucceeds before any runtime search probe.- The requested change can be evaluated through request-parameter passthrough without writing persistent scene, app, dictionary, or recommend configuration.
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.
- today Changed · +4 lines e37227039d40
- 10d ago First seen · 450 lines · 93 tokens per session scan A 9f8917a0f66c
vs-search-tuning-specify-policy-direction is a skill published in the GitHub repository volcengine/SearchCLI (1,175 stars, last pushed today), licensed Apache-2.0. It adds 93 tokens to every session and 5,410 once invoked, about $0.0005 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
sentry
Generated by Gutenberg. Use this skill to call the sentry API through the local sentry CLI.
github
Generated by Gutenberg. Use this skill to call the github API through the local github CLI.
stripe
Generated by Gutenberg. Use this skill to call the stripe API through the local stripe CLI.
espn
Generated by Gutenberg. Use this skill to call the espn API through the local espn CLI.
hacker-news
Generated by Gutenberg. Use this skill to call the hacker-news API through the local hacker-news CLI.
public-holidays
Generated by Gutenberg. Use this skill to call the public-holidays API through the local public-holidays CLI.