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-search-tuningnpx skills add volcengine/SearchCLI --skill vs-search-tuninggit 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)<a href="https://agentmods.dev/skills/volcengine/searchcli/vs-search-tuning"><img src="https://agentmods.dev/badge/skills/volcengine/searchcli/vs-search-tuning.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00029 | $0.03144 |
| Opus 5 | $0.00015 | $0.01572 |
| Sonnet 5 | $0.00006 | $0.00629 |
| Haiku 4.5 | $0.00003 | $0.00314 |
Grade A, and why
vs-search-tuning 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 4d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Viking Search Tuning
When to Use
Use this skill when the user wants an external agent to evaluate and tune text search similarity for an existing AI Search application and dataset.
This first version is for similarity tuning. It defaults to text-query/text-item judging, fixes mode=UserDefined, and tunes the user-defined recall strategy, recall weights, keyword match ratio, and max retrieved count. It can optionally use text+image LLM judging when visual relevance matters; image fields are taken only from GetAppDataConfig.ImageIndexFields. It does not tune rerank, personalization, hotness, boost/bury, sort rules, serving controls, or business operating rules.
Preconditions
- an
application-idis available - a
dataset-idis preferred; if omitted, the CLI can try to infer a unique search dataset from the application - Viking auth is configured with
vs auth status - LLM config is available through
vs llm login,vs llm import-env, orVIKING_LLM_BASE_URL/VIKING_LLM_API_KEY/VIKING_LLM_MODELwhen generating queries or using LLM relevance labels - a query file with
sourceItemIdscan be evaluated with--label-source source-itemfor a fast first-pass silver-label run without LLM relevance judging - the user understands that LLM relevance labels are silver labels and should be reviewed before high-risk production changes
Commands
llm login/llm import-env/llm status: configure and verify OpenAI-compatible LLM credentials without exposing API keys in chat or plain configsearch tune llm-check: verify CLI-managed LLM configurationsearch tune validate: validate a query set locally before planning or running; reports schema issues, duplicate ids/text, sourceItemIds coverage, query type skew, and a label-source recommendationsearch tune query-generate: generate a reusable synthetic query set from paged dataset samples with batched concurrent LLM calls when the user has no query set; add--retrievable-field-onlywhen the user wants generation constrained to textIndexFieldsfrom app dataset config, excludingImageIndexFieldssearch tune plan: show query source, candidate strategies, estimated requests/labels, parameter coverage, source-item coverage, warnings, and suggested first-pass size before runningsearch tune run: generate or load queries, run candidate search strategies, label top results, compute metrics, and write artifacts; supports--label-source llm|source-item|auto,--judge-input text|text-image,--max-judge-images,--llm-retries,--max-label-failure-rate, and--verbose; use--resume-run-id <run-id>to continue an interrupted runsearch tune report: read a previous tuning reportsearch tune compare: compare completed tuning runs with--run-ids, or compare existing scenes online with--scene-ids --queriesusing source-item silver labelssearch tune apply: create a new candidate search scene from a completed tuning report recommendationapp status/doctor: verify app and local environment readiness
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.
- 4d ago First seen · 125 lines · 29 tokens per session scan A a9955c045fec
vs-search-tuning is a skill published in the GitHub repository volcengine/SearchCLI (1,176 stars, last pushed 8d ago), licensed Apache-2.0. It adds 29 tokens to every session and 3,144 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.