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 skills/wangdiandao/godot-devtool/godot-devtoolnpx skills add wangdiandao/godot-devtool --skill godot-devtoolgit clone --depth 1 https://github.com/wangdiandao/godot-devtoolWrote 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/wangdiandao/godot-devtool/godot-devtool)<a href="https://agentmods.dev/skills/wangdiandao/godot-devtool/godot-devtool"><img src="https://agentmods.dev/badge/skills/wangdiandao/godot-devtool/godot-devtool.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.00036 | $0.01943 |
| Opus 5 | $0.00018 | $0.00971 |
| Sonnet 5 | $0.00007 | $0.00389 |
| Haiku 4.5 | $0.00004 | $0.00194 |
Grade A, and why
godot-devtool 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Godot Devtool MCP Router
Compatibility: godot-devtool 3.2.1.
Tool catalog: tools/list is intentionally context-budget-safe and router-only. It exposes only get_capabilities, get_godot_version, and list_projects, plus _meta.toolCategories summaries for route groups, workflows, transports, and risk levels; it has no cursor pagination and no environment-variable fallback to full schemas. All 235 tools and full input schemas are discoverable through filtered get_capabilities. The default get_capabilities response is a lightweight index without input schemas. Request schemas only for the active workflow, routeGroup, exact toolNames, or another narrow filter with includeSchemas: true. Unfiltered schema requests are rejected.
Use this entry skill first. Then keep only the matching domain skill in context:
godot-devtool-project-setup: install or upgrade the addon, inspect projects, configure InputMap/autoload/export settings.godot-devtool-live-editor: use the open Godot editor througheditor_ws, including selection, Inspector, UndoRedo edits, Dock status, andeditor_save_scene.godot-devtool-runtime-test: run the game, prove runtime bridge state throughruntime_ws, simulate input, inspect node properties, and stop runs.godot-devtool-scene-authoring: author scenes/resources/scripts with native and headless Godot tools such asadd_node,get_node_properties, andupdate_node_properties.godot-devtool-release-verify: validate this MCP package, docs, build output, and local Skill sync before release.
Client Setup
Typical local release-zip MCP client configuration:
{
"mcpServers": {
"godot-devtool": {
"command": "node",
"args": ["E:/godot-devtool/build/index.js"],
"env": {
"GODOT_PATH": "D:/Program Files/Godot/Godot_v4.x.exe",
"GODOT_DEVTOOL_WS_PORT": "8766"
}
}
}
}
Codex Desktop uses TOML in config.toml:
[mcp_servers.godot-devtool]
command = "node"
args = ["E:/godot-devtool/build/index.js"]
env = { GODOT_PATH = "D:/Program Files/Godot/Godot_v4.x.exe", GODOT_DEVTOOL_WS_PORT = "8766" }
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 · 166 lines · 36 tokens per session scan A 00a863f71fed
godot-devtool is a skill published in the GitHub repository wangdiandao/godot-devtool (90 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 1,943 once invoked, about $0.0002 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-30.
Other skills, from other repositories
dedicated-server
Use when building dedicated servers — headless export, server architecture, lobby management, and deployment.
dialogue-manager
Use when using the Dialogue Manager addon — .dialogue files with titles, responses, conditions and mutations, runtime balloons, and C# support.
event-bus
Use when implementing decoupled communication between nodes — global EventBus autoload with typed signals.
godot-optimization
Use when optimizing Godot games — profiler, draw calls, physics tuning, memory management, and common bottlenecks.
limboai
Use when using the LimboAI addon — behavior trees and hierarchical state machines (C++ GDExtension) with a visual editor, BTTask subclassing, and a blackboard.
camera-system
Use when implementing cameras — smooth follow, screen shake, camera zones, and transitions for 2D and 3D.