Borrowing it
Nothing to install: this file belongs to dcc-mcp/dcc-mcp-3dsmax. 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/dcc-mcp/dcc-mcp-3dsmax/main/.agents/skills/vx-commands/SKILL.mdgit clone --depth 1 https://github.com/dcc-mcp/dcc-mcp-3dsmaxWrote 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/dcc-mcp/dcc-mcp-3dsmax/vx-commands)<a href="https://agentmods.dev/skills/dcc-mcp/dcc-mcp-3dsmax/vx-commands"><img src="https://agentmods.dev/badge/skills/dcc-mcp/dcc-mcp-3dsmax/vx-commands/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/dcc-mcp/dcc-mcp-3dsmax/vx-commands"><img src="https://agentmods.dev/badge/skills/dcc-mcp/dcc-mcp-3dsmax/vx-commands.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.00059 | $0.01898 |
| Opus 5 | $0.00030 | $0.00949 |
| Sonnet 5 | $0.00012 | $0.00380 |
| Haiku 4.5 | $0.00006 | $0.00190 |
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 11d 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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VX Command Reference
Quick rule: Prefer semantic reduction first:
--jsonwith selected fields, then--jq/vx rgfiltering, then--compactfor broad logs. SetVX_OUTPUT=json,VX_OUTPUT=toon, orVX_OUTPUT=compactonly when you want that default for the whole invocation.
Structured Output Commands (AI-Optimized)
vx-native commands support --json, --toon, --compact, and
--output-format <text|json|toon|compact>. Forwarded tools such as vx git,
vx gh, vx cargo, or vx npm keep their native stdout by default; use the
tool's own structured flags first, or add vx --compact ... when broad
subprocess output must be filtered.
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)
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.
- 11d ago First seen · 252 lines · 59 tokens per session scan A 60c33431a58b
vx-commands is a skill published in the GitHub repository dcc-mcp/dcc-mcp-3dsmax (4 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 1,898 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
maya-render
Pipeline stage — render globals, final-frame rendering, and viewport capture: configure render settings, query them, render frames, capture playblasts. Use for producing final or preview imagery. Not for modeling (maya-mesh-ops), animation editing (maya-animation), generic file import/export (maya-geometry), or render…
maya-scripting
Bootstrap stage — escape hatch for Maya work that has no packaged skill yet. Agents should prefer searchskills / dcccapabilitymanifest → loadskill → typed tools (inputSchema + annotations) from domain skills; use executepython or executemel only when no skill matches, for bulk in-process loops, or for API…
dcc-mcp-maya-setup
Set up dcc-mcp-maya for an agent or operator: install Maya Python dependencies with mayapy, generate MCP host configuration, guide the user through loading the Maya plugin, and run a first live-tool smoke prompt.
maya-import-to-scene
Pipeline stage — structured asset import. Consume an AssetDescriptor produced by maya-asset-source and import the asset (FBX, OBJ, USD) into the current Maya scene via cmds.file(). Handles axis/unit conversion, MaterialMode, PlacementHint, and optional target collection grouping. Returns an ImportToSceneResult with…
maya-asset-source
Pipeline stage — asset discovery and resolution. Search local asset libraries, resolve paths to structured AssetDescriptor records, and surface candidate assets for downstream import. Use before maya-import-to-scene to locate what to import.
maya-mock-async
Synthetic async skill for gateway integration tests. Sleeps for N seconds and reports progress every 500 ms. No actual Maya installation required — uses MayaStandaloneDispatcher.