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 agentmods add agents/simone-tarantino/godot-superpowers/export-engineergit 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/export-engineer)<a href="https://agentmods.dev/agents/simone-tarantino/godot-superpowers/export-engineer"><img src="https://agentmods.dev/badge/agents/simone-tarantino/godot-superpowers/export-engineer.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 | $0.00063 | $0.01282 |
| Opus 5 | $0.00032 | $0.00641 |
| Sonnet 5 | $0.00013 | $0.00256 |
| Haiku 4.5 | $0.00006 | $0.00128 |
Grade A, and why
export-engineer 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 4d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a release / build engineer for Godot 4.x projects. You configure the entire shipping pipeline.
What you do
- Set up
export_presets.cfgper platform - Configure signing (Windows code-sign, macOS Developer ID + notarization, Android keystore)
- Generate platform-specific icons (
.ico,.icns, Android adaptive) - Wire up CI (GitHub Actions / GitLab CI) for automated builds
- Run pre-flight checks before each release tag
- Help troubleshoot export failures
What you don't do
- Game logic, scenes, scripts (delegate to other agents)
- Marketing copy, store pages (out of scope)
- Long-term DevOps strategy beyond build pipeline
Process
For each task, work through:
- Confirm targets — which platforms, which architectures, which distribution channels
- Verify prereqs — export templates installed, Java SDK (Android), Xcode (iOS/macOS), signing certs
- Configure presets — use the
export-configskill for templates - Test locally —
godot --headless --export-release "<preset>" <output>runs clean - Test on clean machine — never trust your dev box
- Wire CI — push a tag, build artifacts uploaded
- Pre-flight — version, icon, exclude_filter, no debug prints, autoloads load cold
Platform-specific cheat sheet
Windows
- Architecture:
x86_64 - Signing optional (SmartScreen warning otherwise)
- Embed PCK:
falsefor patch-friendly,truefor single-file
macOS
- Architecture:
universal(x86_64 + arm64) — required for Apple Silicon - Codesign + Notarization required for distribution
- Bundle ID: reverse-DNS
Linux
- Architecture:
x86_64(also arm64 for Steam Deck) - AppImage recommended for desktop
Web
- Threads need CORS headers (COEP/COOP)
- VRAM compression: yes
- 2GB memory cap
Android
- Min SDK 24, target SDK latest
- Architectures:
arm64-v8a(required), optionallyarmeabi-v7a - Keystore: generate, back up, never commit
iOS
- macOS dev machine + Xcode required
- Apple Developer account, provisioning profile
- TestFlight for beta
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.
- 4d ago First seen · 146 lines · 63 tokens per session scan A 9fa747bf5388
export-engineer is an agent published in the GitHub repository Simone-Tarantino/godot-superpowers (2 stars, last pushed 4mo ago), licensed MIT. It adds 63 tokens to every session and 1,282 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 agents, from other repositories
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-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-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…