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/scarletkc/vexor/vexor-clinpx skills add scarletkc/vexor --skill vexor-cligit clone --depth 1 https://github.com/scarletkc/vexorWrote 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/scarletkc/vexor/vexor-cli)<a href="https://agentmods.dev/skills/scarletkc/vexor/vexor-cli"><img src="https://agentmods.dev/badge/skills/scarletkc/vexor/vexor-cli.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.1 | $0.00046 | $0.01233 |
| Opus 5 | $0.00023 | $0.00616 |
| Sonnet 5 | $0.00009 | $0.00247 |
| Haiku 4.5 | $0.00005 | $0.00123 |
Grade A, and why
vexor-cli 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 6d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vexor CLI Skill
Goal
Find files by intent (what they do), not exact text.
Use It Like This
- Use
vexorfirst for intent-based file discovery. - If
vexoris missing, follow references/install-vexor.md.
Command
vexor "<QUERY>" [--path <ROOT>] [--mode <MODE>] [--ext .py,.md] [--exclude-pattern <PATTERN>] [--top 5] [--content] [--format rich|porcelain|porcelain-z|json]
Common Flags
--path/-p: root directory (default: current dir)--mode/-m: indexing/search strategy--ext/-e: limit file extensions (e.g.,.py,.md)--exclude-pattern: exclude paths by gitignore-style pattern (repeatable;.js→**/*.js)--top/-k: number of results--include-hidden: include dotfiles--no-respect-gitignore: include ignored files.vexorignoreproject rules always apply, even with--no-respect-gitignore.--no-recursive: only the top directory--format:rich(default),porcelain/porcelain-zfor scripts,jsonfor full output with chunk content--content: print each match's source text below the table — usually removes the need to read the files afterwards--no-cache: in-memory only, do not read/write index cachevexor index --local: create and use project-local.vexor/cache storage
Project Config
- The nearest
.vexor/config.jsonapplies automatically for the resolved search or index path. - It accepts only
rerank,auto_index,model,embedding_dimensions,batch_size,embed_concurrency, andextract_concurrency. batch_sizemust be at least0; both concurrency values must be at least1.- Credentials and endpoints (
api_key,base_url,remote_rerank) and all other fields are rejected. - Precedence is global config, project config, environment overrides, then explicit arguments.
vexor config --showlabels each field's origin andvexor doctorlists active overrides; mutatingvexor configcommands remain global-only.
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.
- 6d ago First seen · 108 lines · 46 tokens per session scan A f021b479fad9
vexor-cli is a skill published in the GitHub repository scarletkc/vexor (239 stars, last pushed 8d ago), licensed MIT. It adds 46 tokens to every session and 1,233 once invoked, about $0.0002 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
esm
Comprehensive toolkit for protein language models including ESM3 (generative multimodal protein design across sequence, structure, and function) and ESM C (efficient protein embeddings and representations). Use this skill when working with protein sequences, structures, or function prediction; designing novel…
vs-search-tuning-specify-policy-direction
Viking Search tuning for specified policy directions. Use this when the user provides specific queries, a type of query, or a business policy direction, and asks to boost, suppress, or fix a class of search results through request-parameter passthrough. You must only perform read-only baseline evaluation and…
vs-search-tuning-partial-case
Use when the user provides 1-50 concrete bad-case search queries for one Viking Search app and wants local deterministic fixes. This skill only verifies request-level fine-operation interventions against a read-only baseline scene and delivers a console-ready configuration sheet, validated payloads, and a replay…
ketch
Research skill for ketch — a fast stateless CLI for web search, OSS code search, curated library docs, page scraping, and site crawling; an optional MCP server exists for operators who want it, but the CLI is the primary interface. Use when a question needs live sources: 'research X', 'what are people saying about Y'…
vs-search-tuning
Use when a user asks an agent to evaluate or tune text search similarity for an existing Viking AI Search application and dataset.
vs-search
Search runtime and scene management: verify queries, inspect scenes, debug app readiness, and diagnose recall or scene-config issues.