Borrowing it
Nothing to install: this file belongs to loonghao/rez-next. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/loonghao/rez-next/main/.agents/skills/vx-best-practices/SKILL.mdgit clone --depth 1 https://github.com/loonghao/rez-nextWrote 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/loonghao/rez-next/vx-best-practices)<a href="https://agentmods.dev/skills/loonghao/rez-next/vx-best-practices"><img src="https://agentmods.dev/badge/skills/loonghao/rez-next/vx-best-practices/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/skills/loonghao/rez-next/vx-best-practices"><img src="https://agentmods.dev/badge/skills/loonghao/rez-next/vx-best-practices.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.00031 | $0.02841 |
| Opus 5 | $0.00015 | $0.01421 |
| Sonnet 5 | $0.00006 | $0.00568 |
| Haiku 4.5 | $0.00003 | $0.00284 |
Grade D, and why
vx-best-practices scanned grade D with 2 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 7d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
# ❌ sudo vx install node Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf ~/.nvm How it starts
The opening of the file, as written. The whole thing — 530 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VX Best Practices
Golden rule: Always prefix tool commands with
vxin vx-managed projects. Usevx.tomlfor project-level tool versions, commitvx.lockfor reproducibility, and prefer templates over custom code when creating providers.
General Principles
1. Always Use vx Prefix
In vx-managed projects, always prefix tool commands with vx:
# ✅ Correct
vx npm install
vx cargo build
vx just test
# ❌ Wrong (might use system tools)
npm install
cargo build
just test
2. Prefer Project-Level Configuration
Use vx.toml to ensure consistency across team members:
# ✅ Correct - defined in vx.toml
vx sync
# ❌ Wrong - manual installation
vx install node@22
3. Commit Lock Files
Always commit vx.lock to ensure reproducible builds:
git add vx.lock
git commit -m "chore: update dependencies"
Project Setup
Initial Setup
# 1. Initialize project
vx init
# 2. Add required tools
vx add node@22
vx add go
vx add just
# 3. Generate lock file
vx lock
# 4. Commit configuration
git add vx.toml vx.lock
Team Onboarding
New team members only need to run:
# Clone repository
git clone <repo>
cd <repo>
# One command setup
vx setup
CI/CD Configuration
Use the vx GitHub Action:
# .github/workflows/ci.yml
- uses: loonghao/vx@main
with:
setup: 'true'
cache: 'true'
Version Management
Version Selection Strategy
| Scenario | Constraint | Example |
|---|---|---|
| Development | Major version | node = "22" |
| CI/CD | Exact version | node = "22.0.0" |
| Library | Range | node = ">=18 <23" |
| Latest features | "latest" |
uv = "latest" |
Avoid Over-Specification
# ✅ Good - flexible for patch updates
[tools]
node = "22"
go = "1.22"
# ❌ Bad - too rigid for development
[tools]
node = "22.0.0" # Blocks security patches
go = "1.22.0" # Requires update for each patch
LTS for Production
# Use LTS versions for stability
[tools]
node = "lts" # Auto-updates to latest LTS
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.
- 7d ago First seen · 530 lines · 31 tokens per session scan D b4ddd6217c7d
vx-best-practices is a skill published in the GitHub repository loonghao/rez-next (25 stars, last pushed 3d ago), licensed Apache-2.0. It adds 31 tokens to every session and 2,841 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it D with 2 findings (asks for root, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-02.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.