Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/alexqem/zvec-toolnpx agentmods add rules/alexqem/zvec-tool/zvecWrote 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/rules/alexqem/zvec-tool/zvec)<a href="https://agentmods.dev/rules/alexqem/zvec-tool/zvec"><img src="https://agentmods.dev/badge/rules/alexqem/zvec-tool/zvec/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/rules/alexqem/zvec-tool/zvec"><img src="https://agentmods.dev/badge/rules/alexqem/zvec-tool/zvec.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00765 |
| Opus 5.5 | $0.00000 | $0.00306 |
| Sonnet 5.5 | $0.00000 | $0.00153 |
| Haiku 4.5 | $0.00000 | $0.00076 |
Grade A, and why
zvec 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 1mo 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
zvec — semantic search skill
zvec-tool is a CLI for semantic search over the project knowledge base. It turns documents
into a vector index and retrieves relevant fragments by meaning. Use it to find docs, regulations,
and business-process notes before doing broad greps.
- Model:
intfloat/multilingual-e5-small(384-dim, multilingual) - Indexed scope: the folder you pass to
index(only*.mdby default; configure viaZVEC_EXTENSIONS) - No global DB lock:
withCollectionopens/closes the DB per call, sosearchnever blocksindex
When to use
Call zvec search when you need to:
- find how a business process is described/documented
- locate documentation for a specific entity (справочник/документ/регистр)
- find related regulations or concepts
- get context before changing project configuration
Do not use zvec to search source code or config files — it only indexes the document folder you configured. For code, run a normal grep instead.
Search command
Run from the project root (the parent of zvec-tool/):
node zvec-tool/zvec.mjs search "<query in RU or EN>" --top 8
| Flag | Description |
|---|---|
--top N |
Number of results (default: 8) |
--json |
Machine-readable JSON output |
Examples
node zvec-tool/zvec.mjs search "учёт товаров на складе" --top 5
node zvec-tool/zvec.mjs search "регистр накопления остатки" --top 8
node zvec-tool/zvec.mjs search "порядок закрытия месяца" --top 6
node zvec-tool/zvec.mjs search "документ поступление" --json
Each result contains: the file path, a score (cosine similarity, > 0.7 is strong), and a 220-char preview. Results are sorted by descending score.
Rebuild the index
# Path is required — point it at your documents folder
node zvec-tool/zvec.mjs index ./docs
# or: node zvec-tool/zvec.mjs index --root ./docs
# or set ZVEC_INDEX_ROOT=./docs
Status & diagnostics
node zvec-tool/zvec.mjs status # index status: docCount, active version
node zvec-tool/zvec.mjs doctor # detailed diagnostics (probes DB, shows lock holder)
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.
- 1mo ago First seen · 82 lines · 0 tokens per session scan A ba6b422b137d
zvec is a cursor rule published in the GitHub repository alexqem/zvec-tool (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 765 tokens. 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-31.
Other cursor rules, from other repositories
cardano-mcp
These rules complement our main development collaboration rules, focusing specifically on the Model Context Protocol (MCP) server project with TypeScript. This project serves as a specialized RAG (Retrieval-Augmented Generation) gateway to existing Cardano resources, documentation, and tools to assist with dApp…
005_Dynamo_KV_Cache_Management_KVBM
NVIDIA Dynamo KV Cache Management (KVBM) - Advanced memory management and offloading strategies for optimal performance.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.