author-game-levels

author-game-levels is a skill for Codex from 2233admin/design-pipeline. It costs 54 tokens per session (843 once invoked), scanned A, a copy of author-game-levels, MIT.

A guide for designing readable, flat-world levels for Three.js games, keeping movement, collision, objectives, and encounters on one accessible gameplay plane. Visual height may appear in background decoration but does not change navigation.

In plain words
What is it for?
Use it to author movement routes, arenas, gates, landmarks, pickups, objectives, lighting, and desktop or mobile playthrough checks for browser games.
Why use it?
It helps players understand routes, threats, goals, and exits while keeping level data, collision, navigation, and decoration separate and testable.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it to author movement routes, arenas, gates, landmarks, pickups, objectives, lighting, and desktop or mobile playthrough checks for browser games.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/2233admin/design-pipeline/author-game-levels
Install

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.

Any agent
npx skills add 2233admin/design-pipeline --skill author-game-levels
Clone the repo
git clone --depth 1 https://github.com/2233admin/design-pipeline

Made for: Codex.

Wrote 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.

agentmods badge for author-game-levels

README.md
[![agentmods](https://agentmods.dev/badge/skills/2233admin/design-pipeline/author-game-levels/github.svg)](https://agentmods.dev/skills/2233admin/design-pipeline/author-game-levels)
Your own site
<a href="https://agentmods.dev/skills/2233admin/design-pipeline/author-game-levels"><img src="https://agentmods.dev/badge/skills/2233admin/design-pipeline/author-game-levels/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.

agentmods 80×15 button for author-game-levels

Your own site · 80×15
<a href="https://agentmods.dev/skills/2233admin/design-pipeline/author-game-levels"><img src="https://agentmods.dev/badge/skills/2233admin/design-pipeline/author-game-levels.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 843 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00054 $0.00843
Opus 5 $0.00027 $0.00421
Sonnet 5 $0.00011 $0.00169
Haiku 4.5 $0.00005 $0.00084

Measured 6d ago against content hash df8da94bf505, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

author-game-levels 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 6d 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.

Origin

This is a copy

100% identical to author-game-levels — 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.

skill/references/mengto-skills/upstream/agent-skills/game-development/author-game-levels/SKILL.md · 63 lines

How it starts

The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Author Game Levels

Treat architecture as gameplay communication. Every route, arena, gate, prop, and light must help the player read movement, threats, objectives, or state.

Enforce one gameplay plane

Keep all collision, navigation, encounter routes, objectives, pickups, and player movement on one accessible plane.

  • Do not add stairs, ramps, raised platforms, drop-offs, cliffs, bridges, ledges, pits, or vertical traversal.
  • Do not change gameplay elevation for shortcuts, arenas, hazards, rewards, or visual variety.
  • If visual height is requested later, keep it non-walkable background dressing. It must not alter navigation, camera occlusion, threat visibility, targetability, or player movement.

Separate level systems

Maintain explicit, independently testable layers for:

  • authored level data and stable zone/anchor IDs;
  • visual geometry and non-walkable background dressing;
  • simplified collision geometry;
  • flat navigation data and movement clearance;
  • encounter, enemy, gate, reset, pickup, objective, and exit zones.

Share stable IDs and transforms between layers, but never infer collision, navigation, or encounter boundaries from decoration alone.

Lay out readable play

  1. Define the architectural purpose of each space: traversal, orientation, combat, recovery, reward, transition, or objective.
  2. Preserve clear movement, camera, and dodge corridors at the intended play distance.
  3. Keep threats, pickups, exits, gates, and interaction targets visible before commitment.
  4. Telegraph encounters through visible arena shape, approach, state change, and stable zone anchors.
  5. Deliberately place arenas, gates, checkpoints, retry spawns, and reset paths. Prevent soft locks, duplicate rewards, hidden re-entry, and enemies pursuing through unrelated zones.
  6. Use landmarks, lighting, contrast, and composition to guide without hiding hazards or making the route ambiguous.

Motivate every local light

Attach every local torch, lantern, brazier, or similar light spatially to a visible emitter. Its position, range, color, intensity, shadowing, and occlusion behavior must match what that emitter appears able to produce.

Read the full file on GitHub · 63 lines

Files

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.

Changes

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.

  1. 6d ago First seen · 63 lines · 54 tokens per session scan A df8da94bf505

Subscribe to this mod's changes

author-game-levels is a skill published in the GitHub repository 2233admin/design-pipeline (9 stars, last pushed 6d ago), licensed MIT. It adds 54 tokens to every session and 843 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to author-game-levels, differing in 0 lines, and is treated as a copy.