Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add dcc-mcp/dcc-mcp-maya --skill maya-devgit clone --depth 1 https://github.com/dcc-mcp/dcc-mcp-mayaWrote 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-maya/maya-dev)<a href="https://agentmods.dev/skills/dcc-mcp/dcc-mcp-maya/maya-dev"><img src="https://agentmods.dev/badge/skills/dcc-mcp/dcc-mcp-maya/maya-dev.svg" alt="Measured on agentmods" 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.00081 | $0.00527 |
| Opus 5 | $0.00041 | $0.00264 |
| Sonnet 5 | $0.00016 | $0.00105 |
| Haiku 4.5 | $0.00008 | $0.00053 |
Grade A, and why
maya-dev 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 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.
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.
What it actually says
maya-dev (Pipeline stage)
Development workflow helpers for agents working on Maya Python tools in a live Maya session. The intended loop is:
attach_projectonce for the project root.- Edit files in the normal workspace.
run_checkorreload_modules+run_entrypoint.- Inspect the concise summary, artifact refs, session events, and optional UI screenshot.
Set DCC_MCP_MAYA_DEV_ROOTS to a path-list of trusted roots when a studio
wants to restrict which local projects can be attached.
Scripts
attach_project— Add a development project root to Maya'ssys.pathreload_modules— Purge or reload modules belonging to the attached projectrun_entrypoint— Import and call a Python entrypoint from the projectrun_script— Run a project-local.pyscript with captured outputstart_debugpy— Start a debugpy listener in the Maya process with attach metadatacapture_ui— Capture the Maya main window or a named Qt widget as PNGui_snapshot/ui_find/ui_action— Inspect and operate Maya Qt UI controls, with optional action evidence artifactsmake_node_ref/resolve_node_ref— Build and resolve stable Maya node referencesrun_check— Reload, run an entrypoint, capture diagnostics/artifacts/session events, optionally grab UI
What ships with it
14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- groups.yaml 364 B
- scripts/attach_project.py 376 B runs code
- scripts/capture_ui.py 362 B runs code
- scripts/make_node_ref.py 354 B runs code
- scripts/reload_modules.py 377 B runs code
- scripts/resolve_node_ref.py 363 B runs code
- scripts/run_check.py 354 B runs code
- scripts/run_entrypoint.py 370 B runs code
- scripts/run_script.py 368 B runs code
- scripts/start_debugpy.py 369 B runs code
- scripts/ui_action.py 351 B runs code
- scripts/ui_find.py 345 B runs code
- scripts/ui_snapshot.py 346 B runs code
- tools.yaml 13 KB
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 · 54 lines · 81 tokens per session scan A 78c5e428f6a4
maya-dev is a skill published in the GitHub repository dcc-mcp/dcc-mcp-maya (50 stars, last pushed 8d ago), licensed MIT. It adds 81 tokens to every session and 527 once invoked, about $0.0004 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-30.
Other skills, from other repositories
dcc-mcp-3dsmax-setup
Set up dcc-mcp-3dsmax for an agent or operator: install 3ds Max Python dependencies with 3dsmaxpy, generate MCP host configuration, guide the user through starting the runtime inside 3ds Max, and run a first live-tool smoke prompt.
3dsmax-asset-source
Domain skill — search and resolve assets into validated AssetDescriptor contracts for cross-DCC asset import pipelines. Returns static catalog entries; production sources can layer download helpers or remote resolution without changing the contract.
3dsmax-scene
Domain skill - open, save, merge, inspect, and manage scenes and objects in the current Autodesk 3ds Max session. Use for typed scene lifecycle, nodes, cameras, selection, visibility, parenting, grouping, pivots, transforms, scene metadata, or object cleanup.
3dsmax-animation
Domain skill - inspect timeline settings, batch and verify transform keys, exchange anim-curves v1 data, bake simple animation curves, and control viewport playback in 3ds Max.
3dsmax-asset-import
Domain skill - import 3D assets (FBX, OBJ, 3DS, USD) into the current 3ds Max scene via the AssetDescriptor or MAXtoA USD procedural contracts. Use when the user wants external geometry or a renderable USD stage in the scene.
3dsmax-lookdev
Domain skill - configure OCIO color management, HDR environment lighting, preview materials, and assign renderer-specific materials (Arnold, V-Ray, Scanline) in 3ds Max.