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 agentmods add skills/ukanwat/aaabench/level-designnpx skills add ukanwat/aaabench --skill level-designgit clone --depth 1 https://github.com/ukanwat/aaabenchWrote 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/ukanwat/aaabench/level-design)<a href="https://agentmods.dev/skills/ukanwat/aaabench/level-design"><img src="https://agentmods.dev/badge/skills/ukanwat/aaabench/level-design.svg" alt="Measured on agentmods" 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 | $0.00083 | $0.01901 |
| Opus 5 | $0.00042 | $0.00950 |
| Sonnet 5 | $0.00017 | $0.00380 |
| Haiku 4.5 | $0.00008 | $0.00190 |
Grade A, and why
level-design 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 5d 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
92% identical to level-design — 6 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Level design
A level is a sequence of intentional experiences delivered through space.
Good level design is a process: define the metrics movement is built on, block
out geometry with primitives, play it, then dress it — never the reverse. This
skill is the engine-neutral practice; use godot-tilemap/unity-tilemap-2d to
lay out 2D grids and gridmaps for 3D.
When to use
- Use to plan a level's structure: critical path, pacing, gating, encounters, and where the player learns vs is tested.
- Use the blockout → test → iterate → dress workflow to build a level that plays well before any art exists.
- Use to derive level metrics from the character's movement so geometry is reachable and fair.
When not to use: to generate levels algorithmically, use procedural-gen
(authored and procedural design are complementary). For the engine's tile/grid
painting tools, use godot-tilemap / unity-tilemap-2d. For the movement
abilities the metrics come from, that's the engine movement skill + input-systems.
Core workflow
- Derive metrics first. Measure the character: max jump height and distance, run speed, reach, camera range. Every gap, ledge, and corridor is sized in these units. Lock them before building geometry.
- Blockout (whitebox/greybox). Build the whole level from untextured primitives at correct scale. Validate flow, sightlines, and reachability while changes are cheap. No art yet.
- Define the critical path (start → goal) and the golden path you expect most players to take. Layer optional/secret paths off it.
- Pace the experience. Alternate tension and rest in a deliberate curve; don't run combat-combat-combat. Give the player room to breathe and to anticipate.
- Teach, then test. Introduce each mechanic in a safe space, let the player practice, then test it under pressure. Difficulty rises in a sawtooth, not a straight line.
- Gate with intent. Use locks/keys, abilities, and one-way drops to control order and pacing; guide with light, lines, and landmarks rather than walls.
- Playtest and iterate. Watch real players: where do they get lost, stuck, bored, or killed unfairly? Fix the blockout; only dress when it plays well.
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.
- 5d ago First seen · 145 lines · 83 tokens per session scan A aba0bca1ebc8
level-design is a skill published in the GitHub repository ukanwat/aaabench (378 stars, last pushed 20d ago), licensed MIT. It adds 83 tokens to every session and 1,901 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to level-design, differing in 6 lines, and is treated as a copy.
Other skills, from other repositories
unreal-pie
Domain skill - Unreal Engine Play-In-Editor (PIE) closed-loop verification. Provides PIE lifecycle control (enter/pause/resume/exit), controlled input injection (no OS dependency), viewport screenshot capture, output log snapshot, performance sampling, and Automation Test execution with async job polling. Use for…
unreal-playtest-agent
Domain skill - run screenshot-light PIE playtest episodes with structured entity observations, bounded semantic actions, transition polling, and in-memory traces for QA and external policy or RL runners.
unreal-actors
Domain skill - Unreal Engine actor management: list, spawn, transform, and delete level actors. Use when inspecting or editing actors in the current Unreal Editor level. Not for Content Browser asset import/export - use unreal-assets for that.
unreal-blueprints
Domain skill - Unreal Engine Blueprint editing: create Blueprint classes, add event/function nodes, connect nodes, add variables, and compile. Use when building or modifying Blueprint logic in the Unreal Editor. Not for level actor placement - use unreal-actors for that.
unreal-cinematics
Domain skill — Sequencer shot and keyframe orchestration, camera cut tracks, and Movie Render Queue job setup. Use when creating or editing Level Sequences, authoring camera animation, or preparing an MRQ job in Unreal Engine 5. Not for Blueprint scripting (unreal-blueprints) or runtime playback (unreal-runtime).
unreal-fab-assets
Acquire free Fab marketplace content through Unreal Engine's official Fab integration, then verify the imported Content Browser assets. Use when the user asks to find, download, add, or import Fab or Unreal Marketplace assets. Not for arbitrary file imports - use unreal-assets instead.