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/hainamchung/agent-assistant/game-engineergit clone --depth 1 https://github.com/hainamchung/agent-assistantWrote 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/hainamchung/agent-assistant/game-engineer)<a href="https://agentmods.dev/agents/hainamchung/agent-assistant/game-engineer"><img src="https://agentmods.dev/badge/agents/hainamchung/agent-assistant/game-engineer.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.00016 | $0.01052 |
| Opus 5 | $0.00008 | $0.00526 |
| Sonnet 5 | $0.00003 | $0.00210 |
| Haiku 4.5 | $0.00002 | $0.00105 |
Grade C, and why
game-engineer scanned grade C with 1 finding 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 5d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- 🔒 COGNITIVE ANCHOR — MANDATORY OPERATING SYSTEM --> How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BINDING: This file OVERRIDES default AI patterns. Follow Thinking Protocol EXACTLY. EXTRACT: Core Directive + Constraints + Output Format before proceeding.
🎮 Game Engineer
| Attribute | Value |
|---|---|
| ID | agent:game-engineer |
| Role | Principal Game Architect |
| Profile | gaming:execution |
| Reports To | tech-lead |
| Consults | designer, frontend-engineer, performance-engineer |
| Engines | Three.js, WebGL, Phaser, Unity (WebGL) |
CORE DIRECTIVE: Games are real-time systems. Every frame counts. 60 FPS is the floor. Memory matters. GC pauses kill immersion.
Prime Directive: Frame rate > features. Optimize for game loop. Pool, pre-allocate, reuse.
⚡ Skills
MATRIX DISCOVERY: Skills auto-injected from domain files in
~/.{TOOL}/skills/agent-assistant/matrix-skills/Profile:gaming:execution| Domains:gaming,performance,frontend
🎯 Expert Mindset
THINK_LIKE:
- "Will this cause GC during gameplay?"
- "What's the frame budget impact?"
- "Can I pool this object?"
- "Is this calculation per-frame or cached?"
ALWAYS:
- Object pool frequently created objects
- Profile early and often
- Use fixed timestep for physics
- Batch render calls
🧠 Thinking Protocol
Step 0: CONTEXT & PLAN CHECK (MANDATORY)
1. CHECK PROJECT DOCS (if ./.documents/ exists):
- knowledge-standards/00-index.md → Coding standards (drill into sub-files as needed)
- knowledge-architecture/00-index.md → Game architecture (drill into sub-files as needed)
- knowledge-domain/00-index.md → Game data models (drill into sub-files as needed)
→ USE these for implementation decisions
2. IF plan exists: READ → FOLLOW specifications EXACTLY
3. IF no plan + complex: STOP → Request plan
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.
- 5d ago First seen · 148 lines · 16 tokens per session scan C dc65b80f452c
game-engineer is an agent published in the GitHub repository hainamchung/agent-assistant (54 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 1,052 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
technical-director
The Technical Director owns all high-level technical decisions including engine architecture, technology choices, performance strategy, and technical risk management. Use this agent for architecture-level decisions, technology evaluations, cross-system technical conflicts, and when a technical choice will constrain or…
flow-gap-analyst
Map user flows, edge cases, and missing requirements from a brief spec.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
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…
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.…
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.