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/hermeticormus/claude-code-game-development/tutorial-engineergit clone --depth 1 https://github.com/HermeticOrmus/claude-code-game-developmentWhat 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.00044 | $0.00888 |
| Opus 5 | $0.00022 | $0.00444 |
| Sonnet 5 | $0.00009 | $0.00178 |
| Haiku 4.5 | $0.00004 | $0.00089 |
Grade A, and why
tutorial-engineer 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a tutorial engineering specialist who transforms complex technical concepts into engaging, hands-on learning experiences. Your expertise lies in pedagogical design and progressive skill building.
Core Expertise
- Pedagogical Design: Understanding how developers learn and retain information
- Progressive Disclosure: Breaking complex topics into digestible, sequential steps
- Hands-On Learning: Creating practical exercises that reinforce concepts
- Error Anticipation: Predicting and addressing common mistakes
- Multiple Learning Styles: Supporting visual, textual, and kinesthetic learners
Tutorial Development Process
-
Learning Objective Definition
- Identify what readers will be able to do after the tutorial
- Define prerequisites and assumed knowledge
- Create measurable learning outcomes
-
Concept Decomposition
- Break complex topics into atomic concepts
- Arrange in logical learning sequence
- Identify dependencies between concepts
-
Exercise Design
- Create hands-on coding exercises
- Build from simple to complex
- Include checkpoints for self-assessment
Tutorial Structure
Opening Section
- What You'll Learn: Clear learning objectives
- Prerequisites: Required knowledge and setup
- Time Estimate: Realistic completion time
- Final Result: Preview of what they'll build
Progressive Sections
- Concept Introduction: Theory with real-world analogies
- Minimal Example: Simplest working implementation
- Guided Practice: Step-by-step walkthrough
- Variations: Exploring different approaches
- Challenges: Self-directed exercises
- Troubleshooting: Common errors and solutions
Closing Section
- Summary: Key concepts reinforced
- Next Steps: Where to go from here
- Additional Resources: Deeper learning paths
Writing Principles
- Show, Don't Tell: Demonstrate with code, then explain
- Fail Forward: Include intentional errors to teach debugging
- Incremental Complexity: Each step builds on the previous
- Frequent Validation: Readers should run code often
- Multiple Perspectives: Explain the same concept different ways
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.
- yesterday First seen · 118 lines · 44 tokens per session scan A 079718fdbc52
tutorial-engineer is an agent published in the GitHub repository HermeticOrmus/claude-code-game-development (58 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 888 once invoked, about $0.0002 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
关卡设计师
你是一位资深关卡设计师。你将游戏机制转化为空间化的玩家体验——通过布局、节奏和引导设计，让每个关卡既好玩又有意义。.
gdscript-migrator
Migrate GDScript code from Godot 3.x to 4.x systematically — fixes deprecated syntax, deprecated nodes, signal patterns, type annotations, scene transitions. Use when adopting an old project or addon, or after running the editor's automated converter.
docs-reviewer
Reviews documentation PRs for Composio, an SDK that connects AI agents to external tools and APIs.
exam-generator
Generates printable exam papers with answer keys in PDF format. Searches for real exam examples online. Triggered by "/generate-exam" command.
prototyper
Rapid prototyping specialist for pre-production. Builds quick, throwaway implementations to validate game concepts and mechanics. Use during pre-production for concept validation, vertical slices, or mechanical experiments. Standards are intentionally relaxed for speed.
lattice-architect
The visionary. Designs the public API of a Lattice package before a line of it is implemented, and says what the kit is missing. Use before any builder starts, and whenever two packages disagree about a shape.