Agent Sprite Forge is a Codex-oriented workflow for producing reusable 2D game assets such as sprite sheets, map layers, transparent PNG frames, and animated GIFs. It supports game developers working with Godot, Unity, or other 2D workflows by combining image generation with local processing, asset validation, and engine-ready exports, and its catalogue skills provide the workflow.
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 0x0funky/agent-sprite-forge --skill codeart2dgit clone --depth 1 https://github.com/0x0funky/agent-sprite-forgeWrote 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/0x0funky/agent-sprite-forge/codeart2d)<a href="https://agentmods.dev/skills/0x0funky/agent-sprite-forge/codeart2d"><img src="https://agentmods.dev/badge/skills/0x0funky/agent-sprite-forge/codeart2d/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/0x0funky/agent-sprite-forge/codeart2d"><img src="https://agentmods.dev/badge/skills/0x0funky/agent-sprite-forge/codeart2d.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.00186 | $0.02506 |
| Opus 5.5 | $0.00074 | $0.01002 |
| Sonnet 5.5 | $0.00037 | $0.00501 |
| Haiku 4.5 | $0.00019 | $0.00251 |
Grade A, and why
codeart2d 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 11d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- codeart2d — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Art 2D
You write the art as text (PixelSpec JSON, portable SVG, rig, FX, material, layout or parallax
specs); the scripts render, check and package it. No image model is involved. It is a declared art
source (art_source: "code"), not a placeholder.
Use when
- The user explicitly asks for code-drawn art: a PixelSpec or SVG sprite, palette variants drawn in code, a code rig, code FX, a seam-proven autotile set, a code-made layout, stylized parallax or ambient loops.
route_media.pyprintsno-route(exit 3): no API key is configured and no local image or video route exists. Say so, and offer to add a key or a CLI as well.- Pose and layout guides that help an image model (support material, not final art).
Do not use when
- Any art request while an image or video route exists and the user did not ask for code art: generate2dsprite, generate2dmap or video2dsprite generate it.
- Painterly, organic or identity-rich art, likenesses, portraits, HD-2D plates or textured terrain; realistic fire, smoke or water.
- Never trace licensed characters into specs.
Capability check (once per session)
Run python "<skill-dir>/../generate2dmedia/scripts/route_media.py" resolve --kind image (or --kind video): when it names a route, the image or video skill takes the request unless the user asked for code art. forge_doctor.py in the same folder shows the full picture. If encoding.stdout fails, set PYTHONUTF8=1. For SVG work also run svg_render.py doctor --report <new.json> once per machine.
Art source
This skill is the explicit-only last resort of the route order: the API when a key is configured, then the local image tools, then code art, only when the user asks for it or no route exists. Never substitute it silently for generated art. Before you draw, check what code art can and cannot draw well in style-envelope.md (its table describes strengths, not the route order), and tell the user when a request needs an image model. Disclose every result: "code-drawn, no image model" (codeart-meta.json records "art_source": "code"); never present it as image-model output.
What ships with it
41 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.
- agents/openai.yaml 364 B
- examples/dirt-path.material.json 2.0 KB
- examples/hero.anim.json 2.2 KB
- examples/hero.rig.svg 3.2 KB
- examples/meadow-layout.json 13 KB
- examples/palette.json 447 B
- examples/parallax-gen.json 1.4 KB
- examples/plate-effects.json 1.1 KB
- examples/potion-icons.svg 3.2 KB
- examples/slash.fx.json 2.0 KB
- examples/slime.pixelspec.json 3.3 KB
- examples/walker16x24.pixelspec.json 5.1 KB
- examples/water-grass.material.json 1.4 KB
- references/fx-language.md 9.5 KB
- references/fx-runtime-contract.md 7.3 KB
- references/layouts-and-parallax.md 20 KB
- references/pixelspec.md 11 KB
- references/rasterizers.md 4.9 KB
- references/rig-animation.md 18 KB
- references/runtime/fx-template.mjs 13 KB runs code
- references/schemas/codeart.schema.json 52 KB
- references/schemas/common.schema.json 13 KB
- references/schemas/map.schema.json 128 KB
- references/schemas/sprite.schema.json 65 KB
- references/style-envelope.md 5.1 KB
- references/svg-profile.md 8.4 KB
- references/tiles-and-maps.md 15 KB
- scripts/ambient_bake.py 32 KB runs code
- scripts/autotile_build.py 103 KB runs code
- scripts/codeart_core.py 119 KB runs code
- scripts/forge_core.py 78 KB runs code
- scripts/forge_nav.py 95 KB runs code
- scripts/forge_schema.py 26 KB runs code
- scripts/fx_build.py 49 KB runs code
- scripts/fx_verify.mjs 30 KB runs code
- scripts/layout_build.py 107 KB runs code
- scripts/parallax_build.py 47 KB runs code
- scripts/pixel_qa.py 22 KB runs code
- scripts/render_pixelspec.py 43 KB runs code
- scripts/rig_animate.py 118 KB runs code
- scripts/svg_render.py 26 KB runs code
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.
- 11d ago First seen · 83 lines · 186 tokens per session scan A 6d00b1e35d29
codeart2d is a skill published in the GitHub repository 0x0funky/agent-sprite-forge (4,488 stars, last pushed 11d ago), licensed MIT. It adds 186 tokens to every session and 2,506 once invoked, about $0.0007 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-10-07.
Other skills, from other repositories
img2blockbench
Reconstruct a Minecraft-style creature, character, prop, or vehicle concept as a native Blockbench model using an optional provider-selected 3D mesh, agent vision, and deterministic compilation. Use when Codex should turn PNG, JPEG, or WebP artwork, optionally accompanied by a textured GLB or GLTF from any image-to-3D…
pyxel
Build, debug, and verify games made with Pyxel, the retro game engine for Python. Use whenever a task creates, changes, tests, or reviews a Pyxel game, or asks for a retro Python game that should use Pyxel. Do not use for other engines or general Python work.
Pixel Art Exporter
Export sprites to PNG, GIF, or spritesheet formats with JSON metadata for game engines. Use when the user wants to "export", "save", "output", "render", "generate", "create file", mentions file formats like "PNG", "GIF", "animated GIF", "spritesheet", "sprite sheet", "texture atlas", "tile sheet", or game engine…
Pixel Art Professional
Apply advanced pixel art techniques including dithering, palette optimization, shading, antialiasing, and color theory. Use when the user mentions "dithering", "dither", "Bayer", "Floyd-Steinberg", "palette", "colors", "reduce colors", "optimize palette", "color limit", "shading", "shadows", "highlights", "lighting"…
Pixel Art Creator
Create new pixel art sprites from scratch with canvas creation, layer management, and basic drawing primitives. Use when the user wants to create a sprite, draw pixel art, make a new canvas, start a new image, begin a new project, or mentions pixel dimensions like "64x64", "32x32 sprite", "128 by 128", "16 pixel…
Pixel Art Animator
Create and manage sprite animations with multiple frames, animation tags, frame durations, and linked cels. Use when the user wants to animate a sprite, add animation, create movement, make it move, mentions "animation", "animated", "frames", "keyframes", "frame rate", "FPS", "timing", "duration", "walk cycle", "run…