
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
@vibe-agent-toolkit/cli
Advanced tools
Command-line interface for the Vibe Agent Toolkit.
Install the umbrella package globally:
npm install -g vibe-agent-toolkit
Or install CLI package directly in a project:
npm install @vibe-agent-toolkit/cli
# Show version (with context)
vat --version
# Show help
vat --help
# Show comprehensive help
vat --help --verbose
# Scan markdown resources
vat resources scan docs/
# Validate link integrity
vat resources validate docs/
# Show resources help
vat resources --help --verbose
Index and query markdown documents using vector search:
# Index markdown files into RAG database
vat rag index docs/
# Search the database
vat rag query "authentication methods"
# View database statistics
vat rag stats
# Clear database (rebuild required after)
vat rag clear
Database Options:
.rag-db in project root--db <path> flag on any commandEmbedding Model:
all-MiniLM-L6-v2 (local, fast, free)Diagnose vat setup and environment health.
Usage:
# Check environment and configuration
vat doctor
# Show all checks (including passing ones)
vat doctor --verbose
What it checks:
Exit codes:
0 - All checks passed1 - One or more checks failedExample output:
🩺 vat doctor
Running diagnostic checks...
✅ Node.js version
v22.0.0 (meets requirement: >=20.0.0)
✅ Git installed
git version 2.43.0
✅ Git repository
Current directory is a git repository
✅ Configuration file
Found: vibe-agent-toolkit.config.yaml
✅ Configuration valid
Configuration is valid
✅ vat version
Current: 0.1.0 — up to date
📊 Results: 6/6 checks passed
✨ All checks passed! Your vat setup looks healthy.
Troubleshooting:
If checks fail, doctor provides specific suggestions:
❌ Node.js version
v18.0.0 is too old. Node.js 20+ required.
💡 Upgrade Node.js: https://nodejs.org/ or use nvm
Create vibe-agent-toolkit.config.yaml at project root:
version: 1
resources:
include:
- "docs/**/*.md"
- "agents/**/README.md"
exclude:
- "node_modules/**"
- "**/test/fixtures/**"
validation:
checkLinks: true
checkAnchors: true
allowExternal: true
Set VAT_ROOT_DIR to run from source:
export VAT_ROOT_DIR=/path/to/vibe-agent-toolkit
vat --version # Shows: 0.1.0-dev (/path/to/vibe-agent-toolkit)
vat --help --verbose for the same documentation at runtime# Build
bun run build
# Test (do NOT use 'bun test' directly)
bun run test:unit
bun run test:integration
bun run test:system
# Prepare binaries after build
bun run prepare-cli-bin
MIT © Jeff Dutton
FAQs
Command-line interface for vibe-agent-toolkit
We found that @vibe-agent-toolkit/cli demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.