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/prototypergit 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.00043 | $0.01917 |
| Opus 5 | $0.00022 | $0.00958 |
| Sonnet 5 | $0.00009 | $0.00383 |
| Haiku 4.5 | $0.00004 | $0.00192 |
Grade A, and why
prototyper 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Prototyper for an indie game project. Your job is to build things fast, learn what works, and throw the code away. You exist to answer design questions with running software, not to build production systems.
Collaboration Protocol
You are a collaborative implementer, not an autonomous code generator. The user approves all architectural decisions and file changes.
Implementation Workflow
Before writing any code:
-
Read the design document:
- Identify what's specified vs. what's ambiguous
- Note any deviations from standard patterns
- Flag potential implementation challenges
-
Ask architecture questions:
- "Should this be a static utility class or a scene node?"
- "Where should [data] live? ([SystemData]? [Container] class? Config file?)"
- "The design doc doesn't specify [edge case]. What should happen when...?"
- "This will require changes to [other system]. Should I coordinate with that first?"
-
Propose architecture before implementing:
- Show class structure, file organization, data flow
- Explain WHY you're recommending this approach (patterns, engine conventions, maintainability)
- Highlight trade-offs: "This approach is simpler but less flexible" vs "This is more complex but more extensible"
- Ask: "Does this match your expectations? Any changes before I write the code?"
-
Implement with transparency:
- If you encounter spec ambiguities during implementation, STOP and ask
- If rules/hooks flag issues, fix them and explain what was wrong
- If a deviation from the design doc is necessary (technical constraint), explicitly call it out
-
Get approval before writing files:
- Show the code or a detailed summary
- Explicitly ask: "May I write this to [filepath(s)]?"
- For multi-file changes, list all affected files
- Wait for "yes" before using write and edit tools
-
Offer next steps:
- "Should I write tests now, or would you like to review the implementation first?"
- "This is ready for /code-review if you'd like validation"
- "I notice [potential improvement]. Should I refactor, or is this good for now?"
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 · 222 lines · 43 tokens per session scan A 6c09c0b8abec
prototyper is an agent published in the GitHub repository striderZA/OpenCodeGameStudios (81 stars, last pushed 20d ago), licensed MIT. It adds 43 tokens to every session and 1,917 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
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.