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-devtool-release-verifynpx skills add wangdiandao/godot-devtool --skill godot-devtool-release-verifygit 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-release-verify)<a href="https://agentmods.dev/skills/wangdiandao/godot-devtool/godot-devtool-release-verify"><img src="https://agentmods.dev/badge/skills/wangdiandao/godot-devtool/godot-devtool-release-verify.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.00040 | $0.00413 |
| Opus 5 | $0.00020 | $0.00206 |
| Sonnet 5 | $0.00008 | $0.00083 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
godot-devtool-release-verify 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 5d 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 Release Verify
Load this when editing this MCP package rather than only using it on a Godot project.
Required Static Gates
Run build-heavy verifiers sequentially:
npm.cmd run build
npm.cmd run verify:tools
npm.cmd run verify:skill
npm.cmd run verify:gdscripts
npm.cmd run verify:visualizer
npm.cmd run verify:plugin
npm.cmd run verify:runtime
npm.cmd run verify:process
npm.cmd run verify:security
npm.cmd run verify:all
For README tool table changes, run the generator after build and verify that English and Chinese tables stay in sync.
API Regression
Use a real MCP stdio client or equivalent local MCP call chain:
get_capabilities
get_capabilities { "workflow": "live_editor", "includeSchemas": true }
get_capabilities { "includeSchemas": true }
Default get_capabilities must remain lightweight, include workflow summaries, omit schemas, and reject unfiltered schema requests.
Runtime And Dock Regression
Use E:/test or a fresh fixture:
plugin_install
plugin_status
run_project
get_game_node_properties
simulate_action
get_game_node_properties
stop_project
plugin_status
For editor validation, call plugin_dock_status and verify the structured GDT dock status instead of relying on editor screenshots.
Local Skill Sync
After Skill edits:
npm.cmd run sync:skill
npm.cmd run verify:skill
The repo, build output, and installed Codex Skill copies must have matching version and content hashes.
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.
- 5d ago First seen · 63 lines · 40 tokens per session scan A a4642d746741
godot-devtool-release-verify is a skill published in the GitHub repository wangdiandao/godot-devtool (90 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 413 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
roblox-publish-checklist
Use before publishing or updating a Roblox experience to run evidence-backed release gates for the surfaces that changed.
gm-finalize
Seal the current tag: snapshot the per-tag working docs into docs/tags/ /, write a CHANGELOG entry, run git tag, and reset per-tag runtime state for the next /gm-gdd round. Does NOT package a release — that lives in a separate skill. Explicit invocation only — use /gm-finalize.
roblox-release-operations
Run Roblox release operations. Use for pre-publish checklists, smoke tests, release notes, staged rollout thinking, rollback plans, live issue response, release gates, version readiness, and post-release monitoring.
assets-get-data
Get asset data from the asset file in the Unity project — every serializable field and property. Supports token-saving path-scoped reads via paths or viewQuery. Use 'assets-find' to find the asset first.
gameobject-component-destroy
Destroy one or more Components from a target GameObject. Missing (null) components are skipped — they cannot be destroyed. Use 'gameobject-find' and 'gameobject-component-get' to identify the components first.
gameobject-set-parent
Reparent a batch of GameObjects under a new parent in the currently opened Prefab or active Scene. Per-item failures are reported in the returned status string instead of aborting the batch. Use 'gameobject-find' to locate the GameObjects first.