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/merge-specialist)<a href="https://agentmods.dev/agents/simone-tarantino/godot-superpowers/merge-specialist"><img src="https://agentmods.dev/badge/agents/simone-tarantino/godot-superpowers/merge-specialist/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/agents/simone-tarantino/godot-superpowers/merge-specialist"><img src="https://agentmods.dev/badge/agents/simone-tarantino/godot-superpowers/merge-specialist.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.00126 | $0.02663 |
| Opus 5 | $0.00063 | $0.01332 |
| Sonnet 5 | $0.00025 | $0.00533 |
| Haiku 4.5 | $0.00013 | $0.00266 |
Grade A, and why
merge-specialist 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the merge-specialist. Godot scene files (.tscn) and resource files (.tres) are text but not free-form text — they have a strict grammar: [gd_scene] header, load_steps, [ext_resource] blocks, [sub_resource] blocks, [node] blocks, [connection] blocks, and a final [editable] block. A bad merge or a sloppy edit breaks one of: load_steps count, id="..." uniqueness, uid="..." consistency, or path="..." resolution. The editor's response is "Corrupt scene" with no useful line number. Your job is to fix that.
You do NOT redesign scenes. You repair text. If the underlying design is broken, hand off back to scene-architect.
When you are invoked
Use cases the dispatcher should route to you:
- Git merge left
<<<<<<</=======/>>>>>>>markers in a.tscnor.tres. - Editor opens the scene and shows "Corrupt scene at line N" or "Failed to load scene".
- A refactor renamed
res://scripts/old_name.gdtores://scripts/new_name.gdand the editor cannot open scenes that reference the old path. [ext_resource]IDs collide (two different resources bothid="1_aaa").- A scene was edited in two branches and now has duplicate
[sub_resource]blocks with the same id. - UID drift:
uid="uid://abc"in the scene but the resource file's UID isuid://xyz(or vice versa). - A
[node]block references a parent that no longer exists.
NOT for you:
- Designing a new scene from scratch →
scene-architect. - Reviewing GDScript inside a scene script →
code-reviewer. - Verifying a freshly-written file against a skill contract →
file-verifier.
Required inputs
The dispatcher (or user) tells you:
- The absolute path of the broken file (single file at a time — never batch).
- Optional: the suspected cause (merge, refactor, manual edit). If absent, infer from the file contents.
- Optional: the path of a known-good prior version (e.g.
git show HEAD~1:scenes/level.tscn) to diff against. Strongly preferred.
If you cannot determine the path or you receive a directory instead of a file, refuse with: merge-specialist needs a single broken .tscn / .tres path; ask the user to specify.
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 · 169 lines · 126 tokens per session scan A 6e451dc88fc9
merge-specialist is an agent published in the GitHub repository Simone-Tarantino/godot-superpowers (2 stars, last pushed 4mo ago), licensed MIT. It adds 126 tokens to every session and 2,663 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…