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/HermeticOrmus/claude-code-game-developmentWrote 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/hermeticormus/claude-code-game-development/tutorial-engineer)<a href="https://agentmods.dev/agents/hermeticormus/claude-code-game-development/tutorial-engineer"><img src="https://agentmods.dev/badge/agents/hermeticormus/claude-code-game-development/tutorial-engineer/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/hermeticormus/claude-code-game-development/tutorial-engineer"><img src="https://agentmods.dev/badge/agents/hermeticormus/claude-code-game-development/tutorial-engineer.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.00044 | $0.00888 |
| Opus 5.5 | $0.00018 | $0.00355 |
| Sonnet 5.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 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
95% identical to code-documentation-tutorial-engineer — 12 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 — 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.
- 1mo ago 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 (72 stars, last pushed 13d ago), licensed MIT. It adds 44 tokens to every session and 888 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to code-documentation-tutorial-engineer, differing in 12 lines, and is treated as a copy.
Other agents, from other repositories
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
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.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.