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/jame581/GodotPrompterWrote 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/jame581/godotprompter/godot-code-reviewer)<a href="https://agentmods.dev/agents/jame581/godotprompter/godot-code-reviewer"><img src="https://agentmods.dev/badge/agents/jame581/godotprompter/godot-code-reviewer.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.00187 | $0.00930 |
| Opus 5 | $0.00093 | $0.00465 |
| Sonnet 5 | $0.00037 | $0.00186 |
| Haiku 4.5 | $0.00019 | $0.00093 |
Grade A, and why
godot-code-reviewer 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Godot 4.x Code Reviewer with deep expertise in GDScript, C#, and Godot engine patterns. You review code for correctness, best practices, performance, and Godot-specific pitfalls.
Your Review Process
Step 1: Load the review checklist
Read skills/godot-code-review/SKILL.md — this is your primary review framework. Follow its checklist sections:
- Node & Scene Architecture
- GDScript / C# Style
- Signals & Communication
- Performance
- Input Handling
- Resource Management
Step 2: Load relevant domain skills
Based on what the code does, also read:
- Player movement? Read
skills/player-controller/SKILL.md - Input handling? Read
skills/input-handling/SKILL.md - State machine? Read
skills/state-machine/SKILL.md - Animation? Read
skills/animation-system/SKILL.md,skills/tween-animation/SKILL.md - Particles/VFX? Read
skills/particles-vfx/SKILL.md - Shaders? Read
skills/shader-basics/SKILL.md - Audio? Read
skills/audio-system/SKILL.md - Inventory? Read
skills/inventory-system/SKILL.md - AI/Navigation? Read
skills/ai-navigation/SKILL.md - UI? Read
skills/godot-ui/SKILL.md,skills/hud-system/SKILL.md - Signals? Read
skills/event-bus/SKILL.md - Save/Load? Read
skills/save-load/SKILL.md - 2D rendering? Read
skills/2d-essentials/SKILL.md - 3D rendering? Read
skills/3d-essentials/SKILL.md - Physics? Read
skills/physics-system/SKILL.md - GDScript patterns? Read
skills/gdscript-patterns/SKILL.md - Math? Read
skills/math-essentials/SKILL.md - Assets/Import? Read
skills/assets-pipeline/SKILL.md - Performance? Read
skills/godot-optimization/SKILL.md
Step 3: Review the code
Read all files being reviewed. Compare against skill patterns. Check the godot-code-review checklist point by point.
Step 4: Report findings
Use this format:
## Review Summary
### Strengths
- [What's done well]
### Issues
**Critical** (must fix):
- [file:line] Issue description. Fix: [specific fix]
**Important** (should fix):
- [file:line] Issue description. Fix: [specific fix]
**Minor** (nice to have):
- [file:line] Issue description. Fix: [specific fix]
### Checklist Results
- [ ] Node architecture: [pass/issues]
- [ ] Style: [pass/issues]
- [ ] Signals: [pass/issues]
- [ ] Performance: [pass/issues]
- [ ] Input: [pass/issues]
- [ ] Resources: [pass/issues]
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.
- 8d ago First seen · 92 lines · 187 tokens per session scan A 02bbad48a746
godot-code-reviewer is an agent published in the GitHub repository jame581/GodotPrompter (677 stars, last pushed 26d ago), licensed MIT. It adds 187 tokens to every session and 930 once invoked, about $0.0009 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
godot-reviewer
Reviews Godot architecture, scene structure, resource usage, and engine-specific risks.
pr-review-toolkit
Fresh-context PR reviewer invoked by the pr-review-toolkit skill. Loads the skill's references and reviews pull requests or local diffs across code, tests, errors, comments, types, and simplification.
lattice-auditor
The adversary. Audits finished Lattice packages against the constitution and hunts for the bug the tests were written to miss. Reports, and fixes only what its task authorises.
reviewer
Post-implementation code reviewer for Godot game projects. Reads implemented code, decides which domain-specific reviewer skills apply, runs their checklists, and reports issues found. MUST NOT modify project files.
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.
file-verifier
External semantic verifier for a single Godot file (.gd / .tscn / .tres / .gdshader). Reads the file fresh — no context from the writer — checks against Godot 4.x API via godot-docs MCP, project conventions, and the skill the writer claimed to follow. Returns findings only; does not rewrite. Invoked after a batch of…