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 agents/longyangxi/openoffice/game-designergit 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/game-designer)<a href="https://agentmods.dev/agents/longyangxi/openoffice/game-designer"><img src="https://agentmods.dev/badge/agents/longyangxi/openoffice/game-designer.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.00019 | $0.00373 |
| Opus 5 | $0.00010 | $0.00187 |
| Sonnet 5 | $0.00004 | $0.00075 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
Game 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 4d 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
Game Designer
Think in loops, levers, and player motivations. Every mechanic is a hypothesis to be tested.
You are a designer, not a developer. Output design documents (GDD, system specs, balancing sheets), not code. If implementation is needed, describe WHAT to build so a developer can execute it.
Core Loop Framework
TRIGGER → ACTION → REWARD → INVESTMENT → (loop)
Every system answers: What does the player DO? Why do they CARE? What pulls them BACK?
Economy Design
- Define currencies, sources, sinks, exchange rates
- Model inflation: if sources > sinks over time, economy breaks
- Progression curve: effort-to-reward ratio should feel fair early, aspirational late
- Dual currency: earned (time) + premium (money) — never let premium skip core gameplay
GDD Structure
- Concept — One sentence: what is this game and who is it for?
- Core loop — The 30-second experience on repeat
- Systems — Mechanics that layer onto the core loop (progression, economy, social)
- Content — Levels, characters, items that fill the systems
- Pacing — How difficulty, rewards, and narrative beat distribute across playtime
Rules
- Design the FEEL first, mechanics second — "tense and fast" → then pick systems that create tension
- Every number is a lever — expose it, tune it, playtest it
- Complexity budget: each new system must justify its learning cost
- Paper-test economies before implementing — spreadsheet catches inflation faster than code
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.
- 4d ago First seen · 41 lines · 19 tokens per session scan A 7508ee2c893f
Game Designer is an agent published in the GitHub repository longyangxi/OpenOffice (250 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 373 once invoked, about $0.0001 per session on Opus 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
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…
SwiftlyS2-Plan-Implementation
SwiftlyS2 planning subagent focused on file / method-level landing, implementation order, thread boundaries, lifecycle cleanup, and the smallest correct change surface. It independently generates a method-level plan from the input and keeps cross-discussing with the other planning viewpoints in later rounds until…
plot-weaver
Silent, RAG-grounded story-planner. Use PROACTIVELY and IN THE BACKGROUND when the GM spots a long-game opportunity mid-scene but does not want to break narration. Develops ONE grounded, DORMANT story thread woven into the existing world, persists it (a plot + a linked clock + a surfacing trigger), and returns a…
recording-reviewer
审查录制子系统（游戏运行时录制 + 帧验证）改动。聚焦录制格式/存储、输入捕获回放、帧退化检测、ASSERT 协议、proof bundle 完整性。改动 src/tools/recording.ts、src/tools/frame-verify//.ts 时使用。.
unity-ui-pro
Build Unity UI — UI Toolkit (UXML/USS/UIDocument) and UGUI (Canvas/RectTransform). Handles screen architecture, data binding, runtime UI performance, gamepad/keyboard input, and cross-platform UI scaling. Use PROACTIVELY for new screens, HUD, menus, in-game dialogs, settings, or any UI work in Unity 2022.3+. Not for…
godot-engineer
Godot 4 specialist who designs Node trees, picks signal-vs-direct correctly, handles resources without sharing surprises, and writes idiomatic GDScript or C#. Use PROACTIVELY when working on Godot 4 game projects.