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-troubleshooting/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-troubleshooting)<a href="https://agentmods.dev/skills/dcc-mcp/dcc-mcp-3dsmax/vx-troubleshooting"><img src="https://agentmods.dev/badge/skills/dcc-mcp/dcc-mcp-3dsmax/vx-troubleshooting/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-troubleshooting"><img src="https://agentmods.dev/badge/skills/dcc-mcp/dcc-mcp-3dsmax/vx-troubleshooting.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.00030 | $0.02209 |
| Opus 5 | $0.00015 | $0.01104 |
| Sonnet 5 | $0.00006 | $0.00442 |
| Haiku 4.5 | $0.00003 | $0.00221 |
Grade A, and why
vx-troubleshooting 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 12d 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 — 425 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VX Troubleshooting Guide
Quick triage: Start with
vx doctorfor diagnostics. Usevx --debug <command>for detailed logs. Usevx cache cleanto clear corrupted state. Check exit codes (2=tool not found, 3=install failed, 4=version not found, 5=network error).
Common Issues
Installation Failures
Tool Download Failed
Symptoms: Failed to download <tool>: network error or Connection refused
Solutions:
# Enable CDN acceleration (China users)
vx config set cdn_acceleration true
# Use mirror
vx install node --mirror https://npmmirror.com/mirrors/node
# Retry with verbose output
vx install node --verbose --debug
# Check cache and retry
vx cache clean
vx install node
Checksum Mismatch
Symptoms: Checksum mismatch: expected X, got Y
Solutions:
# Clear corrupted download
vx cache clean
# Reinstall with fresh download
vx install node@22 --force
Permission Denied
Symptoms: Permission denied or Access is denied
Solutions:
# Check VX_HOME permissions
ls -la ~/.vx
# Fix permissions (Unix)
chmod -R u+rw ~/.vx
# Run with elevated permissions if needed
sudo vx install node # Not recommended, use user installation
Version Issues
Version Not Found
Symptoms: Version X not found for <tool>
Solutions:
# List available versions
vx versions node
# Use latest stable
vx install node@latest
# Use LTS version
vx install node@lts
# Check for typos
vx versions node | grep "20"
Version Conflict
Symptoms: Multiple versions installed, wrong version active
Solutions:
# List installed versions
vx list node --installed
# Switch to specific version
vx switch node@20
# Check which version is active
vx which node
# Remove conflicting versions
vx uninstall node@18
PATH Issues
Command Not Found
Symptoms: command not found: node after installation
Solutions:
# Verify vx shim directory is in PATH
echo $PATH | grep -o ".vx/bin"
# Add vx to PATH (add to shell config)
export PATH="$HOME/.vx/bin:$PATH"
# Or use vx directly
vx node --version
# Check shim exists
ls ~/.vx/bin/node
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.
- 12d ago First seen · 425 lines · 30 tokens per session scan F e958c4c21c29
vx-troubleshooting is a skill published in the GitHub repository dcc-mcp/dcc-mcp-3dsmax (4 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 2,209 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-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.