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-commands/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-commands)<a href="https://agentmods.dev/skills/loonghao/rez-next/vx-commands"><img src="https://agentmods.dev/badge/skills/loonghao/rez-next/vx-commands.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00043 | $0.01445 |
| Opus 5 | $0.00022 | $0.00723 |
| Sonnet 5 | $0.00009 | $0.00289 |
| Haiku 4.5 | $0.00004 | $0.00145 |
Grade A, and why
vx-commands 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 6d 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VX Command Reference
Quick rule: All vx commands support
--jsonfor structured output and--format toonfor token-optimized output (saves 40-60% tokens). SetVX_OUTPUT=jsonto default all commands to JSON.
Structured Output Commands (AI-Optimized)
All commands support --json for structured output and --format toon for token-optimized output (saves 40-60% tokens).
Project Analysis
vx analyze --json # Analyze project structure
vx check --json # Verify tool constraints
vx ai context --json # Generate AI-friendly project context
Output fields (analyze):
ecosystems[]- Detected ecosystems (nodejs, python, rust, go)dependencies[]- Project dependenciesscripts[]- Available scriptsrequired_tools[]- Tools needed
Output fields (check):
requirements[]- Tool requirement statusall_satisfied- Whether all constraints are metmissing_tools[]- Tools that need installation
Output fields (ai context):
project- Project info (name, languages, frameworks)tools[]- Installed tools with versionsscripts[]- Available scriptsconstraints[]- Tool constraints
Tool Management
vx list --json # List installed tools
vx versions node --json # List available versions
vx which node --json # Find tool location
vx search <query> --json # Search for tools
Output fields (list):
runtimes[]- Available runtimestotal- Total countinstalled_count- Installed count
Output fields (versions):
versions[]- Available versions with metadatalatest- Latest versionlts- LTS version (if applicable)
Output fields (which):
path- Executable pathversion- Resolved versionsource- Source (vx, system, global_package)
Installation
vx install node@22 --json # Install tool
vx sync --json # Sync from vx.toml
Output fields (install):
runtime- Tool nameversion- Installed versionpath- Installation pathduration_ms- Installation durationdependencies_installed[]- Dependencies also installed
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.
- 6d ago First seen · 210 lines · 43 tokens per session scan A c416a6bc7fdb
vx-commands is a skill published in the GitHub repository loonghao/rez-next (25 stars, last pushed 2d ago), licensed Apache-2.0. It adds 43 tokens to every session and 1,445 once invoked, about $0.0002 per session on Opus 5. 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-02.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.