Why agents need help with game art
Coding agents can write a lot of a game's code, but they're weak on the art. If a sprite needs a pivot point, a collider, a pixels-per-unit value or a check that a walk cycle loops, the agent usually guesses. It can see the files, but it can't reliably judge a frame's ground line or whether frame 56 joins up with frame 1.
On 10 November 2026 Ludo.ai, a Seattle company that makes AI tools for game developers, released 32 free command-line tools inside its Ludo CLI to handle that work. Jorge Gomes, Ludo's co-founder and CTO, said in the announcement that "coding agents are very good at game code, but they still eyeball the art." He said the company made the toolbox free and open source because every game project has to do this kind of setup.
The CLI is MIT-licensed and on GitHub. The toolbox runs on your own machine and doesn't need an account, an API key or credits.
How the toolbox talks to an agent
Each tool is built to be called by a program. It prints plain JSON that lists what it measured, the files it wrote and how confident it is, plus a hint field that suggests the next command. JSON is the default whenever output isn't going to a terminal, and --quiet turns off the hints and progress messages.
There are three design choices worth knowing about before you give this to an agent:
- New files instead of overwrites. Toolbox outputs get new names so your source art stays safe. The exceptions are engine files from
sprite exportand loaders made with--emit, which replace earlier copies, and audio edits, which only overwrite when you pass--in-place. - It stops when it's unsure. If a tool can't read an input or isn't confident about something it detected, such as a sheet's grid, it exits with code 12 and doesn't guess. An agent can treat that as a signal to ask you for the grid size and rerun with
--grid. - Ludo's own sheets carry a stamp. Sheets made by Ludo include a grid stamp the slicer can read. Art from anywhere else depends on detection, so it's more likely to hit that exit code.
The README lists the full set of exit codes (0 for success, 2 for bad usage, 5 for not enough credits, and so on). That gives an agent a clear rule for each outcome without having to parse error text.
What's in the box
You can run ludo toolbox to see the list. The 32 tools fall into five groups:
sprite(13 tools): slice, join, compare, pack, sequence, export, loop, metrics, frames, gif, video, from-video and collide.image(14 tools): recolor, palette, outline, shadow, repeat, trim, pad, scale, flip, rotate, extrude, tiles, convert and contact.audio(3 tools): info, trim and convert.model(1 tool): info, which reports triangle count, rig joints, facing direction, clips and walk speed for a 3D model.asset(1 tool): a folder audit that lists the file types it finds, flags missing pieces and names the Ludo command that would fill each gap. It can also write loaders for Phaser or Pixi.
Ludo's examples give a sense of the output. sprite loop scored three animation takes at 0.99, 0.86 and 0.59, and Ludo says anything at 0.8 or higher loops cleanly. image repeat measured tile seams at 0.82x across and 0.66x down. audio info reported loudness in LUFS, true peak, silence, a 120 BPM tempo and clicks at loop points.
Setting it up
You'll need Node.js 20 or newer and Ludo CLI 0.2.0 or later. The npm listing shows a release published on 12 November 2026. Install it globally with npm install -g @ludoai/cli, or run it once with npx @ludoai/cli.
PNG, WebP, GIF, WAV and MP3 work without anything else. You only need ffmpeg for the video tools and for some audio formats: reading OGG or FLAC, and writing OGG, MP3 or FLAC. The CLI looks for ffmpeg on your PATH and in the usual brew, winget, scoop and choco locations, and LUDO_FFMPEG lets you set a custom path.
Here's how to connect each agent:
- Claude Code:
ludo skill installputs the skill in~/.claude/skills. Add--projectto keep it in the repo's.claude/skillsso your team gets it too. You can also install it as a plugin with/plugin marketplace add Ludo-AI/ludo-cli, then/plugin install ludo@ludo. - Codex, Cursor, GitHub Copilot and other agents that read skills:
npx skills add Ludo-AI/ludo-cli. - Gemini CLI:
gemini extensions install https://github.com/Ludo-AI/ludo-cli. - Anything else: point the agent at
ludo agent-help, or pasteskills/ludo/SKILL.mdinto its instructions.
ludo init creates a .ludo.json project file with defaults such as output folder and engine. It also adds agent notes to AGENTS.md, and adds a Cursor rule if there's a .cursor folder.
A sprite pipeline for Godot or Phaser
Here's a sequence we'd ask an agent to run on a new character sheet:
- Slice the sheet with
sprite slice. If it exits with 12, give it the grid size. - Score the loops with
sprite loopand drop any take under 0.8. - Compare and pack related sheets so every frame shares one size and ground line (Ludo's example normalises a set of knight sheets this way).
- Get colliders from
sprite collide, which reports box and capsule shapes for Godot, Unity, Phaser and Box2D. - Export with
sprite export.--engine godotwrites a Godot 4SpriteFrames.tresfile withres://paths when it's inside a project.--engine texturepackerwrites a JSON atlas that Phaser and PixiJS can load.--engine unitywrites a.png.metaand an.animclip and keeps existing GUIDs.
For tile-based games, image tiles --tiled writes tilesets for Tiled. Since every step returns JSON, the agent can check the numbers before it touches your scene files.
Limits, costs and telemetry
The free part is the measuring and processing layer. Ludo says hand editing is still a job for ImageMagick, Aseprite or TexturePacker. It hasn't published accuracy figures beyond its examples, so check the results on your own art before you trust them.
The same CLI also generates sprites, animations, 3D models, video and audio, and that part isn't free. It needs a Pro or Studio plan and uses credits. ludo pricing shows prices without logging in, --dry-run shows a command's cost without running it, and --max-credits or LUDO_MAX_CREDITS sets a spending cap. New accounts get 30 free credits in the web app.
Telemetry is on by default. Each command sends its name, exit code, duration, flag names, version details and which agent ran it, along with a random install ID. Toolbox runs also send file counts and formats. Ludo says it never sends flag values, file paths, file names, prompts or file contents. To turn it off, set LUDO_TELEMETRY=0 or DO_NOT_TRACK=1, which is worth doing in CI.
Why it matters for New Zealand studios
Most NZ studios are small. NZ On Air's 2026 Game Development Sector Rebate data, released on 8 July 2026, shows 43 recipient studios with $829m in revenue for 2025/26, up 17%. Ninety percent of them are small or medium-sized, and 98% of that revenue came from exports. Those studios had 194 games in development, while full-time equivalent jobs fell from 1,288 to 1,124. For teams that size, it's worth having an agent handle sprite setup.
We'd start small: run the folder audit on one existing project, pick a single character, and have your agent slice, score, pack and export it into a branch. Then compare the colliders and pivots with what you'd set by hand.
Sources
- Ludo Asset Toolbox (Ludo.ai developers)
- Ludo-AI/ludo-cli on GitHub
- @ludoai/cli on npm
- Ludo releases free, open-source toolbox that lets AI coding agents prep game assets (Gamespress)
- NZ games sector shows continued growth as new GDSR data released (NZ On Air)
Build with people working on the same things
Join the Auckland Society for AI: NZ$599 a year with a ForgeBox and the members' projects area. Our Auckland meetups are open to everyone.