assemble-scene

assemble-scene is a skill for Claude Code, Codex from playcanvas/create-playcanvas. It costs 45 tokens per session (644 once invoked), scanned A, original, MIT.

A workflow for building one organised gameplay object from a semantic root, its calibrated 3D visuals, collision shape, physics body, and behaviour.

In plain words
What is it for?
It helps assemble characters, scenery, gameplay entities, model hierarchies, colliders, and physics objects in PlayCanvas Engine, React, or Web Components.
Why use it?
It prevents misplaced models, incorrectly sized colliders, duplicated scaling adjustments, and unclear ownership when objects are created or removed.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps assemble characters, scenery, gameplay entities, model hierarchies, colliders, and physics objects in PlayCanvas Engine, React, or Web Components.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/playcanvas/create-playcanvas/assemble-scene
Install

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.

Any agent
npx skills add playcanvas/create-playcanvas --skill assemble-scene
Clone the repo
git clone --depth 1 https://github.com/playcanvas/create-playcanvas

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for assemble-scene

README.md
[![agentmods](https://agentmods.dev/badge/skills/playcanvas/create-playcanvas/assemble-scene.svg)](https://agentmods.dev/skills/playcanvas/create-playcanvas/assemble-scene)
Your own site
<a href="https://agentmods.dev/skills/playcanvas/create-playcanvas/assemble-scene"><img src="https://agentmods.dev/badge/skills/playcanvas/create-playcanvas/assemble-scene.svg" alt="Measured on agentmods" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 644 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00045 $0.00644
Opus 5 $0.00023 $0.00322
Sonnet 5 $0.00009 $0.00129
Haiku 4.5 $0.00005 $0.00064

Measured 7d ago against content hash f0b4c8bb770f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

assemble-scene 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

skills/assemble-scene/SKILL.md · 54 lines

How it starts

The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Scene assembly

Represent one gameplay object with one named semantic root. Put gameplay position, heading, rigid-body, collision, and behavior on that root. Put calibrated render transforms below it.

Consume the existing tuning record from calibrate-model exactly once. If it is missing, stop and calibrate the model; do not calculate or adjust asset tuning during assembly.

Assembly rules

  • Name roots by gameplay role and use predictable names for repeated instances.
  • Apply model calibration once inside the visual child; never reapply scale, grounding, or authored yaw during placement.
  • Space neighbouring roots by their scaled footprints and pivot offsets from calibrate-model, not by pivot position. A non-90° authored yaw rotates a footprint, so reserve its larger horizontal extent as a conservative radius.
  • Put rigid-body and collision components on the same root. Size colliders from measured bounds.
  • Use local transforms below a parent and world transforms only for semantic roots.
  • Keep UI, effects, cameras, and lights outside gameplay model hierarchies.
  • Remove the root through its authoring surface's lifecycle. Unregister external events it owns.
  • Do not scale rigid-body roots or skinned bones.

Prove placement

Declare intentional support, attachment, or containment relationships between roots. After a rendered frame, measure each relationship at the supported object's actual position. Use a mount point, collision ray, or geometry sample; use a support root's AABB maximum only when its top is flat across the full footprint. Record the signed contact gap: positive means floating and negative means penetration. A relationship name does not exempt the pair from this check.

Union descendant world meshInstance.aabb values for each semantic root and compare unrelated peer roots. Any intersection with positive depth on X, Y, and Z beyond a small tolerance is an unresolved placement failure: move the root from its calibrated footprint, or prove the apparent AABB overlap is empty geometry from at least two materially different views. Never accept one model inside another from a single screenshot.

Read the full file on GitHub · 54 lines

Files

What ships with it

3 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.

Changes

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.

  1. 7d ago First seen · 54 lines · 45 tokens per session scan A f0b4c8bb770f

Subscribe to this mod's changes

assemble-scene is a skill published in the GitHub repository playcanvas/create-playcanvas (53 stars, last pushed 3d ago), licensed MIT. It adds 45 tokens to every session and 644 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-30.