Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add melodic-software/claude-code-plugins/plugin install pixel-artWrote 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/melodic-software/claude-code-plugins/scene)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/scene"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/scene/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/melodic-software/claude-code-plugins/scene"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/scene.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.00184 | $0.01413 |
| Opus 5.5 | $0.00074 | $0.00565 |
| Sonnet 5.5 | $0.00037 | $0.00283 |
| Haiku 4.5 | $0.00018 | $0.00141 |
Grade A, and why
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 17d 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.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scene
Compose a moving pixel-art scene the user opens in any browser.
1. Brief
Follow brief.md: the shared fields, the brief.md
file before the first build, one-line defaults, and the presence-gated /planning:interview
offer (planning owns a numbered-question brief; the in-skill brief is the fallback and the
default). Then add:
- Beats: what happens, in order, and how long each lasts; loop or play once.
- Cast and set: characters (existing sprite specs or new ones), location, time of day.
- Resolution: a fixed logical size such as 160x144, 240x160, 320x180; everything is drawn there and integer-scaled.
- Audio: none, or a WAV path / audio artifact from another tool, passed in explicitly.
Mood, palette, style references, and proportions still come from the shared brief and apply to the cast. When view does not apply, default it to "scene" in the defaults line.
When a cast member is an existing spec with brief.md beside it, read that file and extend it.
Do not re-ask fields it answers. Write this scene's brief.md beside the scene template before
the first build.
2. Author
Follow scene-canvas.md. Write a template HTML
file beside the output:
- Characters come from sprite specs: embed them with
/*EMBED:relative/path.json*/nulland build one offscreen canvas per frame at load, so sprites stay the same source the engine sheet uses. Missing characters: author them first with/pixel-art:spriteor/pixel-art:animate. - Beats are a timeline or state machine driven by a fixed 60 Hz step; sprite cadence stays 8 to 12 fps; every draw lands on integer coordinates.
- Light and fades step through palette colors or Bayer-dither patterns; never alpha, gradients or blur.
- Audio, when given: put
/*WAV:relative/file.wav*/nullin the template.embed.pyinlines adata:audio/wav;base64,...URL (the output stays one file). Play it with WebAudio, started on the first click (browsers block autoplay), and rewind the scene clock on that click so the picture and the loop share a start.
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.
- 17d ago Changed · +12 lines d8d2c9b2be8b
- 18d ago First seen · 86 lines · 184 tokens per session scan A c6d3c6476847
scene is a skill published in the GitHub repository melodic-software/claude-code-plugins (25 stars, last pushed today), licensed MIT. It adds 184 tokens to every session and 1,413 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-09-28.
Other skills, from other repositories
find-shortest-path
For pathfinding and search: shortest path, maze solving, game AI, route planning, graph traversal, BFS/DFS, Dijkstra, A problems.
stack-based-backtrack
For search with undo: explicit decision stack, backtracking when paths fail, depth-first exploration with state restoration.
solve-grid-maze
For 2D grid problems: mazes, board games, tile maps, pixel grids, coordinate systems, cellular automata, flood fill. Uses dict-based Grid class pattern.
use-sparse-set
For sparse data: infinite grids, large spaces with few active elements, membership testing, set operations on coordinates or states.
parallel-orchestrator
Manage parallel Claude Code workstreams using git worktrees. Use when: splitting large tasks across multiple workers, coordinating parallel development, monitoring worker progress, integrating completed work, analyzing work item documents (code reviews, issue lists). Triggers: parallel, orchestrator, worktrees…
generate-tree-structure
For tree/maze generation: spanning trees, random mazes, graph coverage. Uses frontier-based exploration with configurable traversal order.