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/striderZA/OpenCodeGameStudiosWrote 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/commands/striderza/opencodegamestudios/bug-report)<a href="https://agentmods.dev/commands/striderza/opencodegamestudios/bug-report"><img src="https://agentmods.dev/badge/commands/striderza/opencodegamestudios/bug-report.svg" alt="Measured on agentmods" 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.00007 | $0.00032 |
| Opus 5 | $0.00003 | $0.00016 |
| Sonnet 5 | $0.00001 | $0.00006 |
| Haiku 4.5 | $0.00001 | $0.00003 |
Grade A, and why
bug-report 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 3d 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.
What it actually says
Invokes /bug-report skill.
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.
- 3d ago First seen · 9 lines · 7 tokens per session scan A 2a391f5655ce
bug-report is a command published in the GitHub repository striderZA/OpenCodeGameStudios (84 stars, last pushed 26d ago), licensed MIT. It adds 7 tokens to every session and 32 once invoked, about $0.0000 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 commands, from other repositories
bug-triage
Classify bugs, assign severity and priority, and propose next actions.
godot-build-fix
Diagnose and resolve Godot export, script, or project configuration issues.
unity-build-fix
Diagnose and resolve Unity build, editor, package, or configuration issues.
unreal-build-fix
Diagnose and resolve Unreal build, packaging, plugin, or configuration issues.
verify
Run a structured verification pass across implementation, quality, and risk.
web-build-fix
Diagnose and resolve web build, bundling, or deployment issues.