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 SpriteCook/claude-plugin --skill spritecook-build-ui-kitsgit clone --depth 1 https://github.com/SpriteCook/claude-pluginWrote 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/spritecook/claude-plugin/spritecook-build-ui-kits)<a href="https://agentmods.dev/skills/spritecook/claude-plugin/spritecook-build-ui-kits"><img src="https://agentmods.dev/badge/skills/spritecook/claude-plugin/spritecook-build-ui-kits/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/spritecook/claude-plugin/spritecook-build-ui-kits"><img src="https://agentmods.dev/badge/skills/spritecook/claude-plugin/spritecook-build-ui-kits.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.00111 | $0.01698 |
| Opus 5 | $0.00056 | $0.00849 |
| Sonnet 5 | $0.00022 | $0.00340 |
| Haiku 4.5 | $0.00011 | $0.00170 |
Grade A, and why
spritecook-build-ui-kits 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 10d 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.
This is a copy
100% identical to spritecook-build-ui-kits — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SpriteCook Build UI Kits
Use this skill for complete screens and cohesive UI systems. Pair it with spritecook-workflow-essentials for credits, manifests, safe downloads, and shared defaults.
Requires: SpriteCook MCP server connected to your editor. Set up with npx spritecook-mcp setup or see spritecook.ai.
Choose the Right Workflow
- Use the UI-kit workflow for menus, HUDs, inventories, dialogs, settings, overlays, shops, character screens, and other compositions whose parts must share one visual language.
- Use
generate_game_art(mode="ui")only for one isolated icon, badge, button, control, divider, frame, or decoration. - For a new screen, always establish one coherent concept first, then extract production components from that concept. Do not generate unrelated controls independently and try to assemble a visual system afterward.
Default Workflow
- Confirm the UI-kit tools are present, then call
get_credit_balancebefore starting the multi-image workflow. If the tools are missing, refresh or reconnect the SpriteCook MCP integration; do not fall back to independently generating a full screen withmode="ui". - Create the kit with
create_ui_kitand preserve itsid. Keep the defaultmodel="gpt-image-2"unless the user specifically requests Gemini and their account supports 2K Gemini generation. - Establish the concept:
- If the user or agent already has a suitable owned SpriteCook asset ID, pass it as
concept_asset_id. This selects it immediately and skips concept generation. - If the concept is a local file, use
spritecook-upload-assetsfirst, then pass the returned ID asconcept_asset_id. - Otherwise call
generate_ui_kit_concepts, follow progress withget_ui_kit, inspect the returned concept assets, and callselect_ui_kit_conceptwith the strongest option.
- If the user or agent already has a suitable owned SpriteCook asset ID, pass it as
- Call
generate_ui_kit_component_sheets. Omitsheet_countto let SpriteCook plan one to three sheets from the concept. - Follow progress with
get_ui_kituntilstatusissheet_reviewand component-sheet assets are present. - Call
extract_ui_kit_componentswithoutsheet_asset_idsto process every sheet from the selected or latest successful attempt. - Inspect
quality_summaryand the returned component draft programmatically. Confirm names are distinct, each rectangle represents one useful element, state families are sensible, and scalable components are marked correctly. Ifrequires_reviewis true, resolve every relevant warning before finalizing. - Call
finalize_ui_kitwith nocomponentsargument only when the saved draft is sensible andquality_summary.requires_reviewis false. Otherwise supply a corrected component list with fixed names, groups, states, rectangles, scalability, or 9-slice borders. - Preserve the UI-kit ID, finalized component asset IDs, and manifest in the project asset manifest.
What ships with it
1 file 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.
- 10d ago First seen · 81 lines · 111 tokens per session scan A db77c58458ab
spritecook-build-ui-kits is a skill published in the GitHub repository SpriteCook/claude-plugin (17 stars, last pushed 23d ago), licensed MIT. It adds 111 tokens to every session and 1,698 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to spritecook-build-ui-kits, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
ux-design
Guided, section-by-section UX spec authoring for a screen, flow, or HUD. Reads game concept, player journey, and relevant GDDs to provide context-aware design guidance. Produces ux-spec.md (per screen/flow) or hud-design.md using the studio templates.
ux-review
Validates a UX spec, HUD design, or interaction pattern library for completeness, accessibility compliance, GDD alignment, and implementation readiness. Produces APPROVED / NEEDS REVISION / MAJOR REVISION NEEDED verdict with specific gaps.
unity-inspector
Advise on Unity Inspector authoring UX.
threejs-game-ui-designer
Design premium Three.js game UI: HUDs, menus, overlays, pause/win/lose screens, settings, icon controls, touch UI, typography, responsive layout, safe areas, text fit, and UI/world cohesion.
game-ui-ux
Design and build game UI/UX — HUDs, menus, and overlays — that survive every screen: anchor- based responsive layout, resolution/aspect scaling and safe areas, keyboard/gamepad focus navigation, a screen/menu state stack, and event-driven (not polled) HUD updates. Engine- neutral patterns that pair with the detected…
biome-creation
A workflow for placing rocks, trees, plants, and other reusable scene objects into a Unity biome, a themed area of a game world. It also covers regenerating the biome and checking the result with screenshots.