@babylonjs-toolkit/agent weekly downloads statistics

Babylon Toolkit Desktop Agent (1.2.12)

The desktop agent owns the entire pipeline end to end — frontend and UI design, gameplay code, shaders, generated art and audio, 3D models in headless Blender, whole game levels and prefabs in a terminal-driven Unity Editor, the interactive glTF export, the web build, the dev server, and visual QA by screenshotting both Unity and the running browser.

Universal Agent Skills for the Babylon Toolkit web game development framework. Each SKILL.md follows the open standard, so the same file works unchanged in Claude Code, Codex CLI, and GitHub Copilot.

Install

npm install -g @babylonjs-toolkit/agent

or, without installing anything globally:

npx @babylonjs-toolkit/agent install

That installs every skill into every skills directory and the Agent Persona into every global instruction file, on macOS, Linux and Windows, and downloads the Agent Reference with all its sub-documents into ~/.claude/toolkit/reference/ (see The local Agent Reference below). Codex targets also enable outbound network access in their workspace-write configuration. Restart your agent session to pick up the skills, instructions and configuration.

Commands

Command	What it does
bt-agent install	Install skills + persona into every target (the default)
bt-agent update	Fetch the newest release from npm, reinstall it, and prune dropped skills
bt-agent uninstall	Remove what it installed — and nothing else
bt-agent doctor	Verify the install; prints INSTALL OK or lists what is missing
bt-agent targets	Show every target and the paths it writes to
bt-agent bridge	Connect this computer to the App Builder so it can drive Unity and Blender
bt-agent diskinfo	Show where your disk space is going — read-only, macOS, Windows and Linux
bt-agent kill	Free a port or range of ports, stop processes by id, or list listening ports — macOS, Windows and Linux

Option	Effect
--project	Install into the current directory instead of your home directory
--targets claude,agents	Restrict to specific targets
--legacy-codex	Also write ~/.codex/skills for pre-.agents Codex builds
--no-persona	Install skills only; leave instruction files alone
--persona-only	Install/refresh the Agent Persona only; do not copy skills
--no-self-update	update only: reinstall the bundled files; do not fetch npm
--no-reference	Do not download the Agent Reference; agents read it from GitHub
--reference-from <dir>	Install the Agent Reference from a local checkout instead of GitHub (offline, or to try unpublished Reference edits)
--dry-run	Print what would happen and change nothing
--json	Machine-readable output

The local Agent Reference

Agents read the Agent Reference before any Babylon work. bt-agent install and bt-agent update download it — reference.md, every sub-document, the training examples and the 2.7 MB API declarations — into ~/.claude/toolkit/reference/, beside the Unity helper scripts the Reference keeps in ~/.claude/toolkit/ (a --project install uses .claude/toolkit/reference/ in the project). Every link into the Reference repo is rewritten to the local file — in the copy and in the installed skills — and the Reference's curl … -o ~/.claude/toolkit/… download commands become cp from the copy, so agents read files instead of fetching pages:

• Faster and more reliable — no network round trip per document, and no failed fetch stopping a run.
• Fewer tokens — an agent searches a large document and reads only the section it needs, where a fetch is all or nothing (unity-exporter-cli.md and unity-authoring-recipes.md are about 30k tokens each); and nothing reaches it summarized or cut short.
• The same in every agent — Claude Code, Codex, Copilot, Gemini CLI and Antigravity all read files.
• In step with the skills — the copy is the one the installed skills were written against.

The copy comes from GitHub at install time, not from the npm package, so a Reference edit reaches agents with bt-agent update — no npm release needed. If the download fails, an existing copy is kept; with no copy at all, the skills and persona keep the GitHub addresses and agents read the Reference from there. The persona names the local folder and keeps GitHub as the fallback for any file that is missing. Claude Code asks before reading outside the project, so a global install adds one read-only rule — Read(~/.claude/toolkit/reference/**) — to ~/.claude/settings.json (uninstall removes it, and only if the installer added it). It also adds a Claude Code PreToolUse hook on Bash that blocks a sleep N of 3 seconds or more — inside until / while loops too — and points the agent at the Agent Reference's wait.mjs, which waits for a port, URL, file, log line or command output instead; uninstall removes only that hook. bt-agent doctor checks that every local link resolves and says when GitHub has a newer Reference.

Disk usage report

bt-agent diskinfo                 # print the report and save Desktop/disk-report-YYYY-MM-DD-HHMM.txt
bt-agent diskinfo --no-save       # print only
bt-agent diskinfo --out report.txt
bt-agent diskinfo --json          # machine-readable
```…