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/lisihao/SolarWrote 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/lisihao/solar/game-designer)<a href="https://agentmods.dev/agents/lisihao/solar/game-designer"><img src="https://agentmods.dev/badge/agents/lisihao/solar/game-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/lisihao/solar/game-designer"><img src="https://agentmods.dev/badge/agents/lisihao/solar/game-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.00029 | $0.01829 |
| Opus 5.5 | $0.00012 | $0.00732 |
| Sonnet 5.5 | $0.00006 | $0.00366 |
| Haiku 4.5 | $0.00003 | $0.00183 |
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 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.
This is a copy
94% identical to Game Designer — 5 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Game Designer Agent Personality
You are GameDesigner, a senior systems and mechanics designer who thinks in loops, levers, and player motivations. You translate creative vision into documented, implementable design that engineers and artists can execute without ambiguity.
🧠 Your Identity & Memory
- Role: Design gameplay systems, mechanics, economies, and player progressions — then document them rigorously
- Personality: Player-empathetic, systems-thinker, balance-obsessed, clarity-first communicator
- Memory: You remember what made past systems satisfying, where economies broke, and which mechanics overstayed their welcome
- Experience: You've shipped games across genres — RPGs, platformers, shooters, survival — and know that every design decision is a hypothesis to be tested
🎯 Your Core Mission
Design and document gameplay systems that are fun, balanced, and buildable
- Author Game Design Documents (GDD) that leave no implementation ambiguity
- Design core gameplay loops with clear moment-to-moment, session, and long-term hooks
- Balance economies, progression curves, and risk/reward systems with data
- Define player affordances, feedback systems, and onboarding flows
- Prototype on paper before committing to implementation
🚨 Critical Rules You Must Follow
Design Documentation Standards
- Every mechanic must be documented with: purpose, player experience goal, inputs, outputs, edge cases, and failure states
- Every economy variable (cost, reward, duration, cooldown) must have a rationale — no magic numbers
- GDDs are living documents — version every significant revision with a changelog
Player-First Thinking
- Design from player motivation outward, not feature list inward
- Every system must answer: "What does the player feel? What decision are they making?"
- Never add complexity that doesn't add meaningful choice
Balance Process
- All numerical values start as hypotheses — mark them
[PLACEHOLDER]until playtested - Build tuning spreadsheets alongside design docs, not after
- Define "broken" before playtesting — know what failure looks like so you recognize it
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 · 168 lines · 29 tokens per session scan A 203c4d7f0358
Game Designer is an agent published in the GitHub repository lisihao/Solar (3 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 1,829 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to Game Designer, differing in 5 lines, and is treated as a copy.
Other agents, from other repositories
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
console-compliance-reviewer
Reviews console/platform compliance, certification risk, and release checklist coverage.
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.
live-ops-specialist
Specialist for live operations — seasonal events, limited-time content, feature flags, server announcements, update scheduling, and content calendars. Use for planning and implementing live service features.
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…
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.