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 skills add otenta/godot-teacher --skill godot-reviewgit clone --depth 1 https://github.com/otenta/godot-teacherWrote 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/skills/otenta/godot-teacher/godot-review)<a href="https://agentmods.dev/skills/otenta/godot-teacher/godot-review"><img src="https://agentmods.dev/badge/skills/otenta/godot-teacher/godot-review/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/skills/otenta/godot-teacher/godot-review"><img src="https://agentmods.dev/badge/skills/otenta/godot-teacher/godot-review.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.00072 | $0.00775 |
| Opus 5 | $0.00036 | $0.00387 |
| Sonnet 5 | $0.00014 | $0.00155 |
| Haiku 4.5 | $0.00007 | $0.00077 |
Grade A, and why
godot-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 12d 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Godot Review
Same pedagogy as the godot-teacher agent: explain the mechanism, don't hand over the fix. This is a learning review, not a code-fixing pass.
Process
-
Read the target files the user pointed at, and
project.godotif present in the project (checkconfig/featuresfor the actual Godot version/renderer so version-sensitive comments are accurate — don't assume the latest 4.x if the project says otherwise). Don't review from memory or guess at file contents. -
Review for problem categories, not line-by-line fixes. For each finding, explain the mechanism — what's happening and why it matters — not just "this is wrong." Look for things like:
- Physics/state mutated in
_processinstead of_physics_process(or vice versa where it matters). - Brittle
get_node("../Foo/Bar")style paths where@exportor%unique_namewould be more robust. - Godot 3 idioms surviving in 4.x (
KinematicBody2D, old signalconnect()string syntax,onready varwithout@, etc.). - Missed signal opportunities — polling state in
_processwhere a signal would be more idiomatic. _readyordering issues — assuming a sibling/child node is ready before the scene tree guarantees it.- Per-frame allocations —
new()-ing objects, instancing scenes, or heavy string building inside_process/_physics_process. - Anything else that stands out: naming, typing (
@export var x: intvs untyped), unused signals, magic numbers that should be@exported.
- Physics/state mutated in
-
Never write the corrected code. Point to the file and area (
res://path/to/file.gd:lineor the relevant function/node) and describe what's off and why — the user fixes it themselves. Only if the user explicitly invokes the override ("give me the fix," "just write the corrected code," "solve it for me") do you provide the tailored corrected code as text, with a short explanation. Ambiguous requests: ask, don't assume. -
Rate each finding using this structure:
- Mechanism — what's happening and why it's a problem (or a smell).
- Where to look — file/function/line.
- Docs to read — a relevant
docs.godotengine.org/en/stable/...page. If unsure of the exact page/API detail, WebFetch to confirm rather than guessing.
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.
- 12d ago First seen · 37 lines · 72 tokens per session scan A 2b2f10a33559
godot-review is a skill published in the GitHub repository otenta/godot-teacher (3 stars, last pushed 1mo ago), licensed MIT. It adds 72 tokens to every session and 775 once invoked, about $0.0004 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-31.
Other skills, from other repositories
gentleman-trainer
Vim Trainer RPG system patterns for Gentleman.Dots. Trigger: When editing files in installer/internal/tui/trainer/, adding exercises, modules, or game mechanics.
game-builder
Convert any topic into playable browser games. Types: trivia, matching, word puzzles, adventure games. Uses Phaser.js or Kaboom.js.
teach-me
Teach the user to build browser games themselves across sessions, by building real games together. Not for building a game for them.
hr-game-development
Help HR and recruiting teams hire and assess game development candidates across engineering, design, and art disciplines. Use when asked to write a game developer job description, create a gameplay engineer interview, assess a game designers portfolio, build a game studio leveling framework, or similar…
godot-genre-educational
Expert blueprint for educational games including gamification loops (learn/apply/feedback/adapt), progress tracking (student profiles, mastery %), adaptive difficulty (target 70% success rate), spaced repetition, curriculum trees (prerequisite system), and visual feedback (confetti, XP bars). Use for learning apps…
tutorial-workflow
A workflow for designing, reviewing, and testing tutorials and new-player onboarding for a game. It checks whether the tutorial teaches the game’s goals, turns, and cause-and-effect actions rather than merely listing buttons or reading like a rulebook.