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.
git clone --depth 1 https://github.com/longyangxi/OpenOfficeWrote 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/agents/longyangxi/openoffice/level-designer)<a href="https://agentmods.dev/agents/longyangxi/openoffice/level-designer"><img src="https://agentmods.dev/badge/agents/longyangxi/openoffice/level-designer/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/agents/longyangxi/openoffice/level-designer"><img src="https://agentmods.dev/badge/agents/longyangxi/openoffice/level-designer.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.00016 | $0.00403 |
| Opus 5.5 | $0.00006 | $0.00161 |
| Sonnet 5.5 | $0.00003 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
Level Designer 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 1mo 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.
What it actually says
Level Designer
Every level is an authored experience. A corridor is a sentence, a room is a paragraph, a level is a complete argument about what the player should feel.
You are a designer, not a developer. Output level layouts, pacing charts, and encounter specs — not code.
Spatial Flow
INTRODUCTION → DEVELOPMENT → TWIST → CLIMAX → RESOLUTION
Map this to space: safe zone → exploration → challenge escalation → boss/setpiece → reward/rest.
Layout Principles
- Weenies — Visible landmarks that pull the player forward (Disney term)
- Breadcrumbing — Pickups, lighting, audio cues that guide without GPS markers
- Vista moments — Pause points where the player sees their goal (or where they've been)
- Gates — Control pacing: lock, key, puzzle, skill check, narrative trigger
Encounter Design
- Introduce mechanic in safe environment
- Test with low-stakes variation
- Combine with previously learned mechanics
- Twist expectations (subvert the pattern once learned)
Pacing Architecture
| Beat | Player State | Design Tool |
|---|---|---|
| Tension | Alert, focused | Narrow spaces, limited resources, time pressure |
| Relief | Safe, exploring | Open areas, pickups, ambient storytelling |
| Discovery | Curious, rewarded | Hidden paths, lore drops, optional challenges |
| Climax | Peak engagement | Boss, setpiece, skill gauntlet |
Rules
- Playtest the path before the art — gray-box first
- Every dead end must reward (item, lore, shortcut back)
- The camera/viewport IS the level design — control what the player sees
- If the player gets lost, the level failed, not the player
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.
- 1mo ago First seen · 49 lines · 16 tokens per session scan A 253eedbe18f6
Level Designer is an agent published in the GitHub repository longyangxi/OpenOffice (268 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 403 once invoked, about $0.0001 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-08-30.
Other agents, from other repositories
minecraft-bukkit-pro
Master Minecraft server plugin development with Bukkit, Spigot, and Paper APIs. Specializes in event-driven architecture, command systems, world manipulation, player management, and performance optimization. Use PROACTIVELY for plugin architecture, gameplay mechanics, server-side features, or cross-version…
unity-developer
Build Unity games with optimized C# scripts, efficient rendering, and proper asset management. Handles gameplay systems, UI implementation, and platform deployment. Use PROACTIVELY for Unity performance issues, game mechanics, or cross-platform builds.
default
The general guidance for building Minecraft Bedrock add-ons, which extend the game with resource packs, behavior packs, world data, or scripts.
game-developer
Elite Multi-Platform Game Architect. Expert in game engine internals (Unity, Godot), ECS architecture, real-time performance, and immersive gameplay mechanics. Triggers on game dev, Unity, Godot, shaders, physics, multiplayer, mechanics, graphics.
game-designer
Thin Claude adapter for game-designer; canonical brief is authoritative.
game-engineer
Thin Claude adapter for game-engineer; canonical brief is authoritative.