Security audit
Security checks for vulnerabilities and agentic risk
The skill is mostly coherent vx guidance, but it includes raw migration commands that recursively delete user tool-manager directories without safety checks.
Review this skill before installing if you let agents run migration commands. The vx setup guidance is generally purpose-aligned, but do not allow automatic execution of the nvm or pyenv removal commands unless you have confirmed the directory contents are no longer needed and have backups where appropriate.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
Never commit secrets. Use environment variables:
# .env (add to .gitignore)
DATABASE_URL=postgresql://...
API_KEY=secret123
This duplicate finding is the same unsafe deletion command, specifically matched as 'rm -rf ~/.nvm'. While likely intended as cleanup, it still normalizes a high-risk destructive pattern in a skill document that may be acted on automatically.
vx add node@$(cat .nvmrc | tr -d 'v')
rm -rf ~/.nvm
### From pyenv → vx
This duplicate finding is the same unsafe deletion command, specifically matched as 'rm -rf ~/.nvm'. While likely intended as cleanup, it still normalizes a high-risk destructive pattern in a skill document that may be acted on automatically.
vx add node@$(cat .nvmrc | tr -d 'v')
rm -rf ~/.nvm
### From pyenv → vx
This duplicate finding is the same unsafe deletion command, specifically matched as 'rm -rf ~/.pyenv'. The risk is accidental destructive action rather than code execution, but in agent-facing documentation that is still a meaningful safety issue.
vx add uv
rm -rf ~/.pyenv
## Provider Development Best Practices
This duplicate finding is the same unsafe deletion command, specifically matched as 'rm -rf ~/.pyenv'. The risk is accidental destructive action rather than code execution, but in agent-facing documentation that is still a meaningful safety issue.
vx add uv
rm -rf ~/.pyenv
## Provider Development Best Practices
Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.
[env]
NODE_ENV = "development"
DEBUG = "app:*"
# Required variables (vx will warn if missing)
Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.
# Install as regular user, not root
# ❌ sudo vx install node
# vx manages user-level installations
vx install node
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
# 1. Check current Python version
python --version
# 2. Create vx.toml
vx init
# 3. Add uv (recommended Python manager)
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.
No suspicious patterns detected.