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 agents/antgroup/vsag/build-and-testgit clone --depth 1 https://github.com/antgroup/vsagWrote 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/agents/antgroup/vsag/build-and-test)<a href="https://agentmods.dev/agents/antgroup/vsag/build-and-test"><img src="https://agentmods.dev/badge/agents/antgroup/vsag/build-and-test.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.00000 | $0.00567 |
| Opus 5 | $0.00000 | $0.00283 |
| Sonnet 5 | $0.00000 | $0.00113 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
build-and-test 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build And Test
Preferred commands
make debug
make test
make fmt
make lint
make fix-lint
make cov
make release
make pyvsag
Prefer these targets over invoking cmake directly so behavior matches CI.
Development environment
- Recommended: use the published Docker development image
(
vsaglib/vsag:ubuntu). - Maintained CI images use the
ci-x86-*andci-aarch64-*tags and are published to bothvsaglib/vsagon Docker Hub andghcr.io/antgroup/vsagon GitHub Container Registry. - Supported local environments include Ubuntu 20.04+ and CentOS 7+.
- Compiler baseline: GCC 9.4.0+ or Clang 13.0.0+.
- Build baseline: CMake 3.18.0+.
See DEVELOPMENT.md for the full setup walkthrough.
Required tool versions
clang-formatmust be version 15 exactly.clang-tidymust be version 15 exactly.
Do not assume newer versions are acceptable; the repository enforces these versions for consistent formatting and diagnostics. CI will fail otherwise.
Testing expectations
- New features should include tests.
- Bug fixes should include regression coverage.
- Contributions are expected to maintain at least 90% code coverage on the
C++ library code (sources under
src/and public headers underinclude/).make testbuilds and runs the unit + functional suite but does not enable coverage instrumentation. To produce the coverage report locally use themake covflow (which configures the build withENABLE_COVERAGE=ON) followed by running the test binaries andscripts/coverage/collect_cpp_coverage.sh; the equivalent CI coverage workflow enforces the 90% threshold. This threshold is based on the unit-test suite; functional tests undertests/and Python code are not currently included in the coverage metric unless explicitly documented otherwise.
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 First seen · 67 lines · 0 tokens per session scan A eae2c520d5f9
build-and-test is an agent published in the GitHub repository antgroup/vsag (507 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 567 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-09-03.
Other agents, from other repositories
data-pipeline-engineer
Data pipeline specialist: embeddings, chunking strategies, vector indexes, data transformation for AI consumption.
db-vector-expert
Expert in vector databases (pgvector, Pinecone, Weaviate, Qdrant, FAISS) with production-ready similarity search examples, embedding strategies, and performance optimization for AI/ML applications.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.