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 commands/sponticelli/gamedev-claude-plugins/code-reviewgit clone --depth 1 https://github.com/sponticelli/gamedev-claude-pluginsWrote 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/sponticelli/gamedev-claude-plugins/code-review)<a href="https://agentmods.dev/commands/sponticelli/gamedev-claude-plugins/code-review"><img src="https://agentmods.dev/badge/commands/sponticelli/gamedev-claude-plugins/code-review.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 | $0.00019 | $0.00318 |
| Opus 5 | $0.00010 | $0.00159 |
| Sonnet 5 | $0.00004 | $0.00064 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
code-review 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 4d 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
Game Code Review
Review the provided code with game development specific concerns.
Review Checklist
Performance
- Hot path optimizations (update loops, physics callbacks)
- Allocation in update (GC pressure)
- Cache-unfriendly access patterns
- Unnecessary component lookups
- Missing object pooling for frequent spawns
Game-Specific
- Frame-rate independent movement (delta time)
- Input handling best practices
- State machine structure
- Event subscription cleanup
- Save/load considerations
Architecture
- Clear responsibilities
- Appropriate coupling
- Testability
- Debugging support
Common Bugs
- Null reference potential
- Off-by-one errors
- Race conditions
- Order of operations
Output Format
## Code Review: [File/Feature]
### Summary
[One paragraph overview of the code and its quality]
### Issues Found
#### 🔴 Critical
[Bugs or performance issues that need immediate attention]
#### 🟡 Improvements
[Suggested enhancements for code quality]
#### 🟢 Nice-to-Have
[Minor polish suggestions]
### Positive Notes
[What's done well - be specific]
### Suggested Refactors
[If substantial changes would help, describe them]
Review the code the user provides.
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.
- 4d ago First seen · 65 lines · 19 tokens per session scan A 92030a1b3cab
code-review is a command published in the GitHub repository sponticelli/gamedev-claude-plugins (15 stars, last pushed 7mo ago), licensed MIT. It adds 19 tokens to every session and 318 once invoked, about $0.0001 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 commands, from other repositories
sim
Run the EmbodiedGen simulation rendering workflow with sim-cli.
speckit.taskstoissues
Command "speckit.taskstoissues" from akiojin/unity-mcp-server, covering ユーザー入力 and 実行手順.
cert-check
Review the current state against certification and platform compliance expectations.
combat-design
Design or revise combat rules, variables, readability, and tuning direction.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
tech-debt
You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create actionable remediation plans.