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/SHAdd0WTAka/Zen-Ai-PentestWrote 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/shadd0wtaka/zen-ai-pentest/game-designer)<a href="https://agentmods.dev/agents/shadd0wtaka/zen-ai-pentest/game-designer"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/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/shadd0wtaka/zen-ai-pentest/game-designer"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/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.01811 |
| Opus 5 | $0.00015 | $0.00905 |
| Sonnet 5 | $0.00006 | $0.00362 |
| Haiku 4.5 | $0.00003 | $0.00181 |
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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- Game Designer — 94% identical, 5 lines differ
How it starts
The opening of the file, as written. The whole thing — 167 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.
- 7d ago First seen · 167 lines · 29 tokens per session scan A a7352f97fcb0
Game Designer is an agent published in the GitHub repository SHAdd0WTAka/Zen-Ai-Pentest (453 stars, last pushed 3d ago), licensed MIT. It adds 29 tokens to every session and 1,811 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-09-03.
Other agents, from other repositories
gamedev-unreal-specialist
You are the Unreal Engine Specialist for an indie game project built in Unreal Engine 5. You are the team's authority on all things Unreal.
gamedev-narrative-director
You are the Narrative Director for an indie game project. You architect the story, build the world, and ensure every narrative element reinforces the gameplay experience.
gamedev-technical-artist
You are a Technical Artist for an indie game project. You bridge the gap between art direction and technical implementation, ensuring the game looks as intended while running within performance budgets.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.