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 wangdiandao/godot-devtool --skill godot-devtool-scene-authoringgit 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-scene-authoring)<a href="https://agentmods.dev/skills/wangdiandao/godot-devtool/godot-devtool-scene-authoring"><img src="https://agentmods.dev/badge/skills/wangdiandao/godot-devtool/godot-devtool-scene-authoring.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.1 | $0.00031 | $0.00355 |
| Opus 5 | $0.00015 | $0.00178 |
| Sonnet 5 | $0.00006 | $0.00071 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
godot-devtool-scene-authoring 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.
What it actually says
Godot Devtool Scene Authoring
Load this for saved-file scene, resource, script, visual, TileMap, UI, animation, audio, physics, or navigation work.
Inspect First
Request focused schema by route group or exact tool names:
get_capabilities { "routeGroup": "scene", "includeSchemas": true }
get_capabilities { "routeGroup": "resource", "includeSchemas": true }
get_capabilities { "routeGroup": "script", "includeSchemas": true }
Read project state before writing:
filesystem_list
filesystem_read
get_resource_index
get_script_index
resource_dependency_graph
scene_open
get_scene_tree
get_node_properties
Author
Use structured tools:
create_scene
add_node
update_node_properties
node_move
rename_node
node_duplicate
delete_node
save_scene
resource_create
load_sprite
material
shader
script_create
script_write
script_attach
For domain work, load only the needed schema:
ui
animation
tilemap
audio
lighting
physics
navigation
particle
Validate
Run check_gdscript_syntax after script changes and run_project_checks after project-wide changes. Use run_project plus runtime tools when behavior must be proven in a running game.
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 · 66 lines · 31 tokens per session scan A 47e799f9849e
godot-devtool-scene-authoring is a skill published in the GitHub repository wangdiandao/godot-devtool (90 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 355 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
unreal-asset-operation
Query and manage UE assets via UCP. Use when the user asks about asset search, dependencies, referencers, asset CRUD, asset management, getting selected/current assets, opening/closing asset editors, or any editor asset operation in Unreal Engine.
unreal-material-editing
Edit UE material node graphs and properties via text (ReadGraph/WriteGraph). Use when the user asks to add, remove, or rewire material expression nodes, or change material properties like ShadingModel or BlendMode.
unreal-actor-editing
Manage actors in UE levels via UCP. Use when the user asks to spawn, delete, move, duplicate, select, or otherwise manipulate actors in the Unreal Engine editor.
unreal-niagara-editing
Edit Niagara systems, emitters, and scripts via UCP. Use when the user asks to create/modify particle effects, manage emitters, configure modules, set module inputs, edit Niagara script graphs, or any Niagara VFX operation.
unreal-large-blueprint-analysis
Systematically analyze and translate large UE Blueprints (10+ functions) into C++ or other targets. Use when the user asks to convert a Blueprint to C++, audit a complex Blueprint, or understand a large Blueprint's full logic.
unreal-modeling-meshops
A reference skill for editing and repairing 3D meshes in Unreal Engine, a game-development tool. It covers operations such as simplification, remeshing, Boolean changes, voxel processing, subdivision, and basic editing.