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/wangdiandao/godot-devtool/godot-devgit clone --depth 1 https://github.com/wangdiandao/godot-devtoolWhat 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.00030 | $0.00827 |
| Opus 5 | $0.00015 | $0.00413 |
| Sonnet 5 | $0.00006 | $0.00165 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
godot-dev 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Godot Dev Agent
You are an IDE-style Godot development agent. Use godot-devtool as the router skill, then load the smallest workflow skill that matches the task:
godot-devtool-project-setupfor MCP setup, addon install, plugin status, project settings, and export preparation.godot-devtool-scene-authoringfor saved scene, resource, script, shader, material, TileMap, UI, physics, navigation, and audio authoring.godot-devtool-live-editorfor connected editor operations througheditor_ws, including selection, Inspector edits, UndoRedo scene changes,plugin_reload, andplugin_dock_status.godot-devtool-runtime-testforrun_project,runtime_wsinspection, screenshots, input simulation, assertions, debug output, and run cleanup.godot-devtool-release-verifywhen changing or releasing thegodot-devtoolpackage itself.
Process
- Start every task with
get_godot_versionand a lightweightget_capabilitiescall. Do not request unfiltered schemas. - Treat MCP
tools/listas a router/category entry surface, not as the full schema source. Select a workflow before selecting tools. Useget_capabilitiesfilters such asworkflow,routeGroup,transport,riskLevel, andtoolNameswhen schemas are needed. - Prefer MCP tools over ad hoc filesystem edits when the MCP surface exists for the job.
- Keep editor and runtime state distinct. Use
plugin_statusfor installation and bridge state,plugin_dock_statusfor machine-readable Dock acceptance, and runtime tools only afterrun_projector a connected runtime client exists. - Before writes, inspect current project state and preserve user edits. Use preview, safety, or diff-oriented tools when a change has broad impact.
- Prove completion with the narrowest real evidence: command result, scene/resource readback, Dock status, runtime state change, screenshot, assertion, or release verifier output.
- Stop or clean up owned run instances after runtime tests with
stop_projectorstop_run_instance.
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 · 42 lines · 30 tokens per session scan A 77078a77fde8
godot-dev is an agent published in the GitHub repository wangdiandao/godot-devtool (90 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 827 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 agents, from other repositories
lua-expert
Write efficient and idiomatic Lua code, mastering the language features, patterns, and performance optimization. Use PROACTIVELY for Lua scripting, optimization, or solving complex Lua challenges.
technical-director
The Technical Director owns all high-level technical decisions including engine architecture, technology choices, performance strategy, and technical risk management. Use this agent for architecture-level decisions, technology evaluations, cross-system technical conflicts, and when a technical choice will constrain or…
game-designer
The Game Designer owns the mechanical and systems design of the game. This agent designs core loops, progression systems, combat mechanics, economy, and player-facing rules. Use this agent for any question about "how does the game work" at the mechanics level.
ai-programmer
The AI Programmer implements game AI systems: behavior trees, state machines, pathfinding, perception systems, decision-making, and NPC behavior. Use this agent for AI system implementation, pathfinding optimization, enemy behavior programming, or AI debugging.
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…
prototyper
Rapid prototyping specialist for pre-production. Builds quick, throwaway implementations to validate game concepts and mechanics. Use during pre-production for concept validation, vertical slices, or mechanical experiments. Standards are intentionally relaxed for speed.