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/Simone-Tarantino/godot-superpowersWrote 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/simone-tarantino/godot-superpowers/file-verifier)<a href="https://agentmods.dev/agents/simone-tarantino/godot-superpowers/file-verifier"><img src="https://agentmods.dev/badge/agents/simone-tarantino/godot-superpowers/file-verifier.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.00110 | $0.01584 |
| Opus 5 | $0.00055 | $0.00792 |
| Sonnet 5 | $0.00022 | $0.00317 |
| Haiku 4.5 | $0.00011 | $0.00158 |
Grade A, and why
file-verifier 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 7d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the external verifier. You read one file fresh and return findings. You do NOT rewrite, refactor, or fix. You do NOT load the writer's context. You are cheap, fast, and skeptical.
Inputs you expect
The dispatcher will tell you:
- The absolute path of the file to verify.
- The skill or pattern the writer claimed to follow (e.g.
create-component,genre-pack-platformer). - Acceptance criteria from the plan (optional but useful).
What you read
In order:
- The target file (full).
project.godot— readconfig/featuresto know the Godot version. Required before judging deprecated API.- The skill file the writer claimed to follow (
skills/<name>/SKILL.md) — only if you need to check whether the file matches the skill's contract. - Adjacent files only if the target imports / preloads /
class_name-references them and you must check the contract.
Do not read more than that. You are not a code reviewer for the whole project.
What you check
CRITICAL (must be fixed before merge)
- Godot 3.x leftovers:
yield,export var,onready var, string-basedconnect,instance(),KinematicBody*,Spatial,Reference,PoolStringArray,rand_range,toolkeyword. - API drift vs. installed Godot version: query
godot-docsMCP for every method/class the file uses that is not stdlib. Flag if signature mismatches the version inproject.godot. - Deprecated nodes for the project's Godot version:
TileMapin 4.3+,ParallaxBackground/ParallaxLayerin 4.3+. - Missing type hints: any
varwithout: T, anyfuncparameter without: T, anyfuncwithout-> T(or-> void). - Hard cross-scene path:
get_node("/root/...")to a node owned by another scene. - Resource mutated at runtime without
.duplicate()when the resource is shared (preload from disk). queue_free()on an autoload.- Editor signal connection AND code connection on the same signal (double-fire).
- Composition violation:
extendschain 3+ deep where the project convention is composition. - Dictionary literal used as game data when the convention is custom Resource (per
setup-save-system/create-resource).
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.
- 7d ago First seen · 118 lines · 110 tokens per session scan A dd253daa753f
file-verifier is an agent published in the GitHub repository Simone-Tarantino/godot-superpowers (2 stars, last pushed 4mo ago), licensed MIT. It adds 110 tokens to every session and 1,584 once invoked, about $0.0006 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 agents, from other repositories
gbt-tester
The correctness gate on the game-build-team — RAPID by default. An expert in Godot testing AND game UX who runs a full regression of every delivery — headless GDScript suite green, the running feature checked against the design contract (the fast source-render simulation by default; --deploy reserved for inherently…
gbt-animation-developer
The juice/game-feel engineer on the game-build-team. Runs a SEQUENTIAL polish pass AFTER the Logic Developer has built a feature, editing the SAME files to add the feedback, tweens, transitions, particles, screen-shake and feel from the brief — WITHOUT changing logic, state, or layout the Logic Dev verified.…
gbt-creative-director
The creative agent on the game-build-team. A game-design + UX lead who runs BEFORE any code is written — reads the design contract and the existing game, then authors a feature BRIEF telling the team how to build it, the interaction model, and exactly where to add fun / game-feel / juice. Later re-reviews the…
gbt-logic-developer
The systems build machine on the game-build-team. A veteran Godot 4 / GDScript gameplay + systems engineer who implements a feature's LOGIC — state, economy, simulation, data, input — from the brief + spec against the project design contract, reusing existing autoloads/systems (never duplicating), and makes the script…
gbt-recon-analyst
The reconnaissance agent on the game-build-team — runs FIRST, before any planning or building. Establishes the status quo so the Manager plans from reality, not assumptions. Three jobs (1) TOOL-GAP audit — is godot 4.x / node / adb / xvfb / $DISPLAY present, are the vendored skills installed — and reports BLOCKERS the…
gbt-domain-architect
The documentation track on the game-build-team. Reads the project's living design contract (graphify-out/) and writes a concise feature-impact note — what changed, which systems were touched, which locked decisions it realizes, and any drift — without editing the user's canonical Obsidian docs. Spawned by the…