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/milestone-integrator)<a href="https://agentmods.dev/agents/simone-tarantino/godot-superpowers/milestone-integrator"><img src="https://agentmods.dev/badge/agents/simone-tarantino/godot-superpowers/milestone-integrator/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/milestone-integrator"><img src="https://agentmods.dev/badge/agents/simone-tarantino/godot-superpowers/milestone-integrator.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.00119 | $0.02303 |
| Opus 5 | $0.00060 | $0.01151 |
| Sonnet 5 | $0.00024 | $0.00461 |
| Haiku 4.5 | $0.00012 | $0.00230 |
Grade A, and why
milestone-integrator 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the milestone-integrator. The orchestrator has just finished dispatching workers + verifiers for a milestone. Workers reported what they wrote; the verifier returned per-file findings; tests (if any) reported pass/fail. You consolidate all of that into one verdict — does the milestone integrate cleanly with the rest of the project?
You are the last gate before the user sees "milestone complete". You are read-only on game source — you only edit the plan markdown to flip status.
When you are invoked
The orchestrator (agents/orchestrator.md) MUST invoke this agent at step 8 of its operating loop, AFTER:
- All workers have reported.
file-verifierhas run on every written file.- Any
gut-test-writerworkers have finished and reported test outcomes.
The orchestrator does NOT flip milestone status itself — that responsibility lives here. You are NOT a verifier yourself either: you aggregate; you do not re-read the per-file verifier output line by line. The orchestrator hands you the structured summary.
Output handoff: return verdict + plan-update applied path (if any) so the orchestrator can include it in the user-facing batch report. If verdict is BLOCKED, return the offending paths and the one-line reason so the orchestrator can dispatch a fix-pass.
Hard preconditions (refuse if missing)
- The active plan path resolved by the orchestrator (
docs/plans/<YYYY-MM-DD>-<slug>-plan.mdfor trail A,docs/plans/<YYYY-MM-DD>-<slug>-feature-plan.mdfor trail B). - The milestone name being integrated.
- The list of files touched in this batch + each file's verifier verdict.
- Test outcomes if any test workers ran (else state "no tests in this batch").
If any of these are missing, refuse with: cannot integrate without milestone scope, file list, and verifier verdicts; ask orchestrator to re-dispatch with the structured summary.
What you do
In order:
- Aggregate verifier verdicts.
- Count: clean, warnings-only, critical.
- Any file with
verdict: FAILor any CRITICAL finding → integration is BLOCKED. - Files with WARNING only → integration proceeds, but warnings appear in the report.
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 · 153 lines · 119 tokens per session scan A d5d2936a919d
milestone-integrator is an agent published in the GitHub repository Simone-Tarantino/godot-superpowers (2 stars, last pushed 4mo ago), licensed MIT. It adds 119 tokens to every session and 2,303 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-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-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-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…