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-substance3d-designer --skill designer-pluginsgit clone --depth 1 https://github.com/dcc-mcp/dcc-mcp-substance3d-designerWrote 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-substance3d-designer/designer-plugins)<a href="https://agentmods.dev/skills/dcc-mcp/dcc-mcp-substance3d-designer/designer-plugins"><img src="https://agentmods.dev/badge/skills/dcc-mcp/dcc-mcp-substance3d-designer/designer-plugins/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-substance3d-designer/designer-plugins"><img src="https://agentmods.dev/badge/skills/dcc-mcp/dcc-mcp-substance3d-designer/designer-plugins.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.00035 | $0.00604 |
| Opus 5.5 | $0.00014 | $0.00242 |
| Sonnet 5.5 | $0.00007 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
designer-plugins 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 1mo 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
Designer Plugins
Honest capability boundary
Designer does not expose a general plugin install, load, or unload API through its Python SDK. This skill is therefore read-only discovery: it reports the node modules that a running Designer build actually provides, and probes which manager APIs exist. It never installs, loads, unloads, or mutates anything.
The authoritative plugin surface is the graph's node-definition inventory — the
same inventory create_node validates against. If a node type is not in that
inventory, create_node will reject it.
Tools
list_node_modules— group every available node definition into its owning module namespace (for examplesbs::compositing,sbs::filter) with a count. Use it first to learn which plugin families exist.describe_node_module— list the definitions owned by one module, optionally filtered by a case-insensitive query. Fails withMODULE_NOT_FOUNDwhen the namespace has no matches.module_capabilities— read-only attribute probe. Reports which application manager methods (getModuleMgr,getPackageMgr,getAppInteropMgr,getQtForPythonUIMgr) and which SDK modules (sd.api.sdmodule,sd.api.sddefinition) this build advertises. A missing API is reported asfalse; absence is an expected result, not a failure.
Module namespace convention
A definition id such as sbs::compositing::blur belongs to module
sbs::compositing (the first two segments). Definitions without a namespace are
reported under <root> rather than being silently dropped.
The module manager, when present, is reported as a supplementary list. Prefer the definition inventory: it is the surface node creation is validated against.
See also
designer-effects and designer-lighting resolve recipe node types against
this same inventory, which is why they fail closed with RECIPE_UNAVAILABLE
instead of assuming a type exists.
What ships with it
4 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.
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.
- 1mo ago Changed 271dbea5fb59
- 1mo ago First seen · 61 lines · 35 tokens per session scan A 45e24cad49b0
designer-plugins is a skill published in the GitHub repository dcc-mcp/dcc-mcp-substance3d-designer (3 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 604 once invoked, about $0.0001 per session on Opus 5.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-20.
Other skills, from other repositories
painter-project
Host skill - inspect and author the current Substance 3D Painter project. Use when creating or checking projects, building uniform or texture-driven PBR layers, masks and generators, baking mesh maps, importing resources, or exporting. Not for arbitrary JavaScript execution.
painter-lighting
Inspect and control Substance 3D Painter scene lighting. Painter has no light objects, so lighting is the environment map and its exposure and rotation. Use when setting up an HDRI, matching a look-dev environment, or reading the current lighting configuration. Not for lamps, shadows, or light rigs.
painter-material
Inspect and author the channel-level material surface of a Substance 3D Painter layer stack. Use when reading which channels a stack carries, enabling or disabling the channels a layer contributes, or setting uniform channel values. Not for creating layers, importing textures, or painting strokes.
painter-compositing
Inspect and control how a Substance 3D Painter layer composites with the layers beneath it - visibility, opacity, blending mode, and mask state. Use when stacking layers non-destructively or tuning how one layer combines with another. Not for creating or deleting layers, and not for painting strokes.
painter-diagnostics
Read-only readiness diagnostics for a running Substance 3D Painter adapter.
photoshop-layers
Adobe Photoshop layer operations — create, delete, reorder, duplicate, rename, set opacity/visibility, fill, blend modes.