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 regiellis/godot-mcp-go --skill swallowtailgit clone --depth 1 https://github.com/regiellis/godot-mcp-goWrote 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/regiellis/godot-mcp-go/swallowtail)<a href="https://agentmods.dev/skills/regiellis/godot-mcp-go/swallowtail"><img src="https://agentmods.dev/badge/skills/regiellis/godot-mcp-go/swallowtail/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/regiellis/godot-mcp-go/swallowtail"><img src="https://agentmods.dev/badge/skills/regiellis/godot-mcp-go/swallowtail.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.00000 | $0.13002 |
| Opus 5 | $0.00000 | $0.06501 |
| Sonnet 5 | $0.00000 | $0.02600 |
| Haiku 4.5 | $0.00000 | $0.01300 |
Grade A, and why
swallowtail 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 2d 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 — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Swallowtail
swallowtail carries one workflow across the running Godot editor, the game process, and the debugger over a WebSocket the Swallowtail editor addon hosts. Discover the live API, create scenes, add nodes, write scripts, play the game, simulate input, inspect state, diagnose failures, apply fixes, and verify the result without leaving the interface. Every editor mutation goes through Godot's UndoRedo, so the user can Ctrl+Z anything.
Prerequisites (check first)
- The Godot editor must be open with the
swallowtailaddon enabled. When a command fails because the editor isn't reachable, runswallowtail status(preflight) rather than guessing. It returns averdict:runningmeans reachable. Never launch another editor (a second instance stacks and breaks discovery).startingmeans the process is alive but still booting. Wait a few seconds and retry; do not launch.crashedmeans a stale discovery file remains but the process is gone. Tell the user it crashed; you may relaunch exactly one editor.closedmeans no discovery file, so the editor closed cleanly or never started. You may launch exactly one editor if the task needs it.- Launch with
swallowtail launch [--headless](run it from inside the project, or pass--project DIR). It applies these same verdict rules itself, starts the editor detached, and sends its output to<project>/.godot/swallowtail-launch.loginstead of your terminal, which a raw launch corrupts. It waits until the editor accepts connections and exits non-zero if it never does. Where the CLI is not installed, the fallback isgodot --path <project> --editor. Relaunch at most once; if it's still unreachable after one attempt, stop and report rather than looping launches. After a successful launch,statuswill readrunning/starting, which is your guard against opening a second. - Check
project_matchtoo.statusreports which project the answering editor serves. When another project's editor holds the port, the verdict readsclosed/crashed(nothing is serving this project) withproject_match: falseand the answeringproject_path, so follow the verdict and open one for this project. Commands refuse to run in that state rather than editing the other project, which is what the check exists to prevent.
- The CLI binary. In this repo:
task build→bin/swallowtail.exe. Invoke asbin/swallowtail.exe <group> <command> [--flags](ortask run -- <group> <command> [--flags]). Elsewhere, use the installedswallowtail. - Connection is automatic. The CLI finds the port from
<project>/.godot/swallowtail.json(written by the addon) when run from inside the project dir; otherwise pass--port(default 9080).
What ships with it
31 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- ai-steering.md 10 KB
- audio-music.md 15 KB
- boss-patterns.md 18 KB
- character-3d.md 18 KB
- csharp-godot.md 7.6 KB
- deckbuilder-patterns.md 13 KB
- environment-art.md 15 KB
- event-deck-games.md 5.7 KB
- game-patterns.md 36 KB
- game-trailers.md 29 KB
- gdscript-architecture.md 9.9 KB
- gdscript-style.md 6.9 KB
- in-game-docs.md 16 KB
- level-design.md 57 KB
- lighting-2d.md 6.1 KB
- menus-settings.md 18 KB
- mobile-touch.md 7.2 KB
- multiplayer-patterns.md 16 KB
- narrative-game-patterns.md 17 KB
- platformer-2d.md 9.4 KB
- porting-godot-versions.md 35 KB
- project-structure.md 7.6 KB
- rhythm-games.md 4.1 KB
- run-based-games.md 12 KB
- save-systems.md 15 KB
- shaders-vfx.md 15 KB
- shipping-export.md 25 KB
- tile-constraint.md 10 KB
- topdown-2d.md 8.6 KB
- ui-polish-2d.md 8.4 KB
- unreal-import-cleanup.md 8.9 KB
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.
- 2d ago First seen · 293 lines · 0 tokens per session scan A f52d3cbd7f63
swallowtail is a skill published in the GitHub repository regiellis/godot-mcp-go (61 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 13,002 tokens. 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-09-08.
Other skills, from other repositories
pi-loop-forensics
Diagnose pi-go agent loops and degenerate turns — "agent loop aborted", runaway thinking with no tool calls, repeated phrases. Discriminates genuine model repetition collapse from a race, a tool-parse failure, or a too-low guard, and A/B replays a seed session across providers.
aibridge-code-index
Optional read-only AIBridge Code Index lightweight lookup for Unity C# declaration names. Use only when Root Rule declares Code Index enabled and this Skill is installed. Map declaration names to files or positions. Do not use for references, callers, implementations, derived types, diagnostics, comments, strings, or…
nightly-session-watch
Nightly sweep of the last 24h of pi-go sessions — anomalous runs, loop aborts, tool error rates, token waste, real prompt-token spend, and whether the observation and palace pipelines are still recording. Triages each finding to the specialist skill that diagnoses it. Use for an unattended daily health check, or on…
hz-vr-debug
Debugs Meta Quest and Horizon OS VR/MR applications using the metavr CLI — view logs, capture screenshots, diagnose common issues. Use when troubleshooting crashes, errors, or unexpected behavior on Quest devices.
test-fix
Diagnose and minimally fix a failing test, then re-run.
hz-perfetto-debug
Analyzes Meta Quest and Horizon OS VR performance using Perfetto traces — frame timing, CPU/GPU bottlenecks, render pass analysis. Use when profiling frame drops, jank, or thermal issues on Quest devices.