Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/yurineko73/Godot-MCP-Nativenpx agentmods add skills/yurineko73/godot-mcp-native/releaseWrote 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/yurineko73/godot-mcp-native/release)<a href="https://agentmods.dev/skills/yurineko73/godot-mcp-native/release"><img src="https://agentmods.dev/badge/skills/yurineko73/godot-mcp-native/release/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/yurineko73/godot-mcp-native/release"><img src="https://agentmods.dev/badge/skills/yurineko73/godot-mcp-native/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.00613 |
| Opus 5 | $0.00015 | $0.00307 |
| Sonnet 5 | $0.00006 | $0.00123 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
release 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 10d 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
Release Godot MCP Native
Use this skill when asked to release a new version of the Godot MCP Native plugin and gdmcp CLI.
Prerequisites
- Rust toolchain installed at
.gdmcp/(or system-wide cargo) - Godot 4.6.1 at
F:\Godot\Godot_v4.6.1-stable_win64.exe - Python 3 with
test/integration/dependencies ghCLI authenticated withyurineko73/Godot-MCP-Nativerepo access
Workflow
1. Run the release script
.\scripts\release.ps1 -Version <X.Y.Z>
This automates:
- Version bump in
plugin.cfg,cli_release.json,mcp_types.gd,Cargo.toml - Full test suite (Rust tests + clippy + GUT + packaging)
- CLI package build (Windows x64; Linux/macOS built separately)
- Plugin archive (
dist/godot-mcp-native-X.Y.Z.zip) - GitHub Release draft with artifacts uploaded
Use -DryRun to preview without changes. Use -SkipTests for quick iteration.
2. Build other platform packages (on their respective hosts)
# Linux
./cli/gdmcp/scripts/package.sh X.Y.Z x86_64-unknown-linux-gnu
# macOS
./cli/gdmcp/scripts/package.sh X.Y.Z x86_64-apple-darwin
./cli/gdmcp/scripts/package.sh X.Y.Z aarch64-apple-darwin
Upload the resulting zip files to the GitHub Release draft.
3. Manual steps
- Submit
godot-mcp-native-X.Y.Z.zipto Godot Asset Library - Upload packages to Quark cloud drive (share link pre-configured in cli_release.json; update only if Quark generates a new link)
- Publish the GitHub Release draft
- Commit version bump:
git commit -m "chore: bump version to X.Y.Z"
4. Verify the release
After publishing:
# Install from GitHub Release
gdmcp --json doctor
# Verify the plugin panel shows correct version in Godot editor
Troubleshooting
- If
gh release createfails, checkgh auth status - If Rust tests fail, run
cargo test --manifest-path cli/gdmcp/Cargo.tomldirectly - If GUT fails, open the project in Godot editor and run tests interactively
- If packaging tests fail, check
test/integration/test_gdmcp_packaging.py
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.
- 10d ago First seen · 71 lines · 29 tokens per session scan A f83fabc26e3c
release is a skill published in the GitHub repository yurineko73/Godot-MCP-Native (768 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 613 once invoked, about $0.0001 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
build-game-changelog
Design, implement, backfill, audit, and release in-game changelogs with contiguous versioning, deployment provenance, menu-state navigation, accessible toggle, close, and Escape behavior, and responsive release-ledger UI. Use when Codex needs to add or revise a changelog or version screen in a game, reconstruct…
writing-modpack-changelog
Use when cutting a modpack release. Creates /docs/release-changelog.md if absent; appends a new version section with grouped changes. Triggers - 'cut a release', 'release notes', 'changelog', 'v1.2.3 changes', 'what changed since last version'.
flame-harness-build
Phase 8 — bootstrap signing credentials, generate fastlane config from templates, and build + upload signed IPA (TestFlight) and AAB (internal track).
roblox-publish-checklist
Use before publishing or updating a Roblox experience to run evidence-backed release gates for the surfaces that changed.
changelog
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
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.