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/5throck/ai-workspace-standardsWrote 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/5throck/ai-workspace-standards/game-debugger)<a href="https://agentmods.dev/agents/5throck/ai-workspace-standards/game-debugger"><img src="https://agentmods.dev/badge/agents/5throck/ai-workspace-standards/game-debugger/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/5throck/ai-workspace-standards/game-debugger"><img src="https://agentmods.dev/badge/agents/5throck/ai-workspace-standards/game-debugger.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.00067 | $0.01988 |
| Opus 5 | $0.00034 | $0.00994 |
| Sonnet 5 | $0.00013 | $0.00398 |
| Haiku 4.5 | $0.00007 | $0.00199 |
Grade A, and why
game-debugger 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 7d 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.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 7d ago First seen · 209 lines · 67 tokens per session scan A 73cc39f79d4b
game-debugger is an agent published in the GitHub repository 5throck/ai-workspace-standards (12 stars, last pushed today), licensed AGPL-3.0. It adds 67 tokens to every session and 1,988 once invoked, about $0.0003 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-09-03.
Other agents, from other repositories
metal_shader_expert
You are a veteran graphics engineer with 20+ years experience at Weta Digital and Pixar, specializing in Metal shaders, real-time rendering, and creative visual effects. You love playful experimentation, clear exposition, and building powerful internal debug tools.
tools-programmer
The Tools Programmer builds internal development tools: editor extensions, content authoring tools, debug utilities, and pipeline automation. Use this agent for custom tool creation, editor workflow improvements, or development pipeline automation.
godot-game-architect
Use this agent when the user needs help with Godot 4.x game development architecture, GDScript or C# system design, scene tree planning, state machines, signal patterns, or designing new features. This includes planning new features, designing game systems, refactoring existing code, debugging architectural issues, or…
unity-diagnostics
Use to investigate Unity connection, compilation, console, scene-health, runtime-state, rendering, memory, or performance problems through Unity Biome MCP. Do not use to implement fixes.
godot-build-resolver
Resolves Godot export, project configuration, and script/runtime build blockers.
performance-reviewer
Reviews CPU, GPU, memory, loading, and budget risk across systems and content.