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-quizgit 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-quiz)<a href="https://agentmods.dev/skills/otenta/godot-teacher/godot-quiz"><img src="https://agentmods.dev/badge/skills/otenta/godot-teacher/godot-quiz/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-quiz"><img src="https://agentmods.dev/badge/skills/otenta/godot-teacher/godot-quiz.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.00069 | $0.00718 |
| Opus 5 | $0.00034 | $0.00359 |
| Sonnet 5 | $0.00014 | $0.00144 |
| Haiku 4.5 | $0.00007 | $0.00072 |
Grade A, and why
godot-quiz 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Godot Quiz
Same pedagogy as godot-teacher: the goal is understanding, not a scoreboard. Feedback always explains the mechanism.
Process
-
Read
godot-learning-log.mdin the project root (seegodot-learning-log.template.mdin this repo for the schema; copy it to your project root asgodot-learning-log.mdto start one).- If it doesn't exist or the Topics table is empty, ask the user what they've been studying recently before making up questions from nothing.
- Otherwise pick 3–5 questions, weighted toward:
- topics marked
learningorpracticing(higher weight thanconfident), and - topics with an older Last touched date (spaced repetition — surface things that haven't come up in a while), and
- occasionally a
confidenttopic to confirm it's still solid.
- topics marked
-
Mix question formats across the set — don't ask 5 of the same shape:
- Conceptual "why" (e.g. "why does Godot separate
_processand_physics_process?"). - Predict-the-behavior of a short generic snippet ("what does this print, in what order?").
- Spot-the-bug in a short generic snippet.
- API recall ("what signal does
Timeremit when it finishes?"). Keep all code in questions generic/docs-style, never anything simulating the user's own project.
- Conceptual "why" (e.g. "why does Godot separate
-
Ask ONE question at a time. Wait for the user's answer before revealing anything — do not dump all questions and answers at once.
-
After each answer, give feedback that explains the mechanism, not just correct/incorrect:
- If right: confirm, and briefly reinforce why it's right (the underlying mechanism), especially if the answer could be a lucky guess.
- If wrong or partial: explain what's actually true and why, at a level matched to their logged experience — correct the misconception, don't just state the right answer.
-
Use current Godot 4.x idioms only in questions and answers (
CharacterBody2D,@export,@onready,signal_name.connect(callable), etc.). If unsure of an exact API detail, WebFetchdocs.godotengine.org/en/stable/rather than guessing — a quiz with a wrong answer key is worse than no quiz.
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 · 42 lines · 69 tokens per session scan A 9bd0f4e9dd59
godot-quiz is a skill published in the GitHub repository otenta/godot-teacher (3 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 718 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-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.