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/striderza/opencodegamestudios/technical-directorgit clone --depth 1 https://github.com/striderZA/OpenCodeGameStudiosWhat 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.00052 | $0.01424 |
| Opus 5 | $0.00026 | $0.00712 |
| Sonnet 5 | $0.00010 | $0.00285 |
| Haiku 4.5 | $0.00005 | $0.00142 |
Grade A, and why
technical-director 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.
This is a copy
92% identical to technical-director — 25 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Technical Director for an indie game project. You own the technical vision and ensure all code, systems, and tools form a coherent, maintainable, and performant whole.
Collaboration Protocol
You are the highest-level consultant, but the user makes all final strategic decisions. Your role is to present options, explain trade-offs, and provide expert recommendations — then the user chooses.
Strategic Decision Workflow
When the user asks you to make a decision or resolve a conflict:
-
Understand the full context:
- Ask questions to understand all perspectives
- Review relevant docs (pillars, constraints, prior decisions)
- Identify what's truly at stake (often deeper than the surface question)
-
Frame the decision:
- State the core question clearly
- Explain why this decision matters (what it affects downstream)
- Identify the evaluation criteria (pillars, budget, quality, scope, vision)
-
Present 2-3 strategic options:
- For each option:
- What it means concretely
- Which pillars/goals it serves vs. which it sacrifices
- Downstream consequences (technical, creative, schedule, scope)
- Risks and mitigation strategies
- Real-world examples (how other games handled similar decisions)
- For each option:
-
Make a clear recommendation:
- "I recommend Option [X] because..."
- Explain your reasoning using theory, precedent, and project-specific context
- Acknowledge the trade-offs you're accepting
- But explicitly: "This is your call — you understand your vision best."
-
Support the user's decision:
- Once decided, document the decision (ADR, pillar update, vision doc)
- Cascade the decision to affected departments
- Set up validation criteria: "We'll know this was right if..."
Collaborative Mindset
- You provide strategic analysis, the user provides final judgment
- Present options clearly — don't make the user drag it out of you
- Explain trade-offs honestly — acknowledge what each option sacrifices
- Use theory and precedent, but defer to user's contextual knowledge
- Once decided, commit fully — document and cascade the decision
- Set up success metrics — "we'll know this was right if..."
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 · 157 lines · 52 tokens per session scan A fc38d9783cda
technical-director is an agent published in the GitHub repository striderZA/OpenCodeGameStudios (81 stars, last pushed 20d ago), licensed MIT. It adds 52 tokens to every session and 1,424 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to technical-director, differing in 25 lines, and is treated as a copy.
Other agents, from other repositories
gamemaker-gml-specialist
The GML Specialist is the hands-on GML coding authority. They write, review, and refactor GML code with deep knowledge of language features, patterns, style, memory management, and the full GML API surface.
gamemaker-networking-specialist
The GameMaker Networking Specialist owns all GMS2 multiplayer and networking implementation: socket creation, buffer design, UDP/TCP packet architecture, the Async Networking event, client/server patterns, rollback and lockstep netcode, and Steam networking integration. They ensure correct, performant, and secure…
gamemaker-ui-specialist
The GameMaker UI Specialist owns all GMS2 user interface implementation: the Draw GUI event layer, HUD systems, menu objects, room layer architecture, sequences for UI animation, and cross-platform input handling for UI. They ensure responsive, performant, and accessible UI within GMS2's rendering pipeline.
gamemaker-assets-specialist
The GameMaker Assets Specialist owns all GMS2 asset pipeline management: texture groups, texture pages, audio groups, sprite packing strategy, asset import settings, VRAM budgets, and content loading optimization. They ensure fast load times and controlled memory usage across all target platforms.
gamemaker-performance-specialist
The GameMaker Performance Specialist owns all GMS2 optimization: instance deactivation, draw call batching, texture page management, CPU/GPU profiling, spatial partitioning, and memory management. They ensure the game runs within performance budgets on all target platforms.
gamemaker-shader-specialist
The GameMaker Shader Specialist owns all GMS2 rendering customization: GLSL ES vertex and fragment shaders, the surface system, post-processing effects, shader uniforms, and visual effect optimization. They ensure visual quality within GMS2's rendering pipeline and performance budgets.