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 nguyenchiencong/godot-mcp-cli --skill godot-debugginggit clone --depth 1 https://github.com/nguyenchiencong/godot-mcp-cliWrote 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/nguyenchiencong/godot-mcp-cli/godot-debugging)<a href="https://agentmods.dev/skills/nguyenchiencong/godot-mcp-cli/godot-debugging"><img src="https://agentmods.dev/badge/skills/nguyenchiencong/godot-mcp-cli/godot-debugging.svg" alt="Measured on agentmods" 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.00092 | $0.00826 |
| Opus 5 | $0.00046 | $0.00413 |
| Sonnet 5 | $0.00018 | $0.00165 |
| Haiku 4.5 | $0.00009 | $0.00083 |
Grade A, and why
godot-debugging 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 7d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Godot Debugging
Critical rule
Debugger tools require the project to run in debug mode: start with run_project (F5) or run_specific_scene, never run_current_scene (F6). F6 runs without the debugger, and debugger tools will report no active session.
Quick start
godot-mcp debugger_enable_events
godot-mcp debugger_set_breakpoint --script-path "res://player.gd" --line 42
godot-mcp run_project
godot-mcp debugger_get_current_state
Call debugger_enable_events FIRST, before setting breakpoints, to receive real-time breakpoint-hit and execution-change notifications.
Workflows
Breakpoint debugging
-
Enable events and set breakpoints, then run the project (F5 mode):
godot-mcp debugger_enable_events godot-mcp debugger_set_breakpoint --script-path "res://player.gd" --line 42 godot-mcp debugger_get_breakpoints godot-mcp run_project -
When the breakpoint hits, inspect state and the stack panels:
godot-mcp debugger_get_current_state godot-mcp debugger_get_call_stack godot-mcp get_stack_frames_panel --refresh true godot-mcp get_stack_trace_panel -
Step through or resume:
godot-mcp debugger_step_over godot-mcp debugger_step_into godot-mcp debugger_resume_execution -
Clean up:
godot-mcp debugger_clear_all_breakpoints godot-mcp debugger_disable_events
Error triage
-
Clear the panels to establish a baseline, reproduce the failure (run the project, exercise the game), then collect evidence:
godot-mcp clear_debug_output godot-mcp clear_editor_errors godot-mcp run_project godot-mcp get_debug_output godot-mcp get_editor_errors -
Inspect the live scene and evaluate expressions (evaluation requires the runtime debugger bridge autoload):
godot-mcp get_runtime_scene_structure --include-properties true --max-depth 3 godot-mcp evaluate_runtime_expression --expression "position" --context-path "/root/Main/Player"
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.
- 7d ago First seen · 97 lines · 92 tokens per session scan A f58941f86966
godot-debugging is a skill published in the GitHub repository nguyenchiencong/godot-mcp-cli (11 stars, last pushed 3d ago), licensed MIT. It adds 92 tokens to every session and 826 once invoked, about $0.0005 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-31.
Other skills, from other repositories
minecraft-debug-mcp
Operate and debug the live Minecraft bot through its built-in MCP REPL server. Use when work requires starting the bot with pnpm dev, connecting to the local MCP endpoint, inspecting cognitive state/logs/history, injecting synthetic chat/events, or running targeted REPL code against the running brain during…
graphics-api-hooking
Guide for graphics API interception, overlay rendering, and render-pipeline analysis across DirectX, OpenGL, and Vulkan. Use this skill when working with Present or SwapBuffers hooks, DXGI swap chains, shader or draw-call interception, screenshot-sensitive overlays, or graphics debugging in game security research.
console-get-logs
Retrieve Unity Editor logs from the MCP plugin's LogCollector, optionally filtered by log type or time window. Useful for debugging and monitoring Editor activity.
editor-application-get-state
Return the current state of UnityEditor.EditorApplication — playmode, paused state, compilation state, and related flags.
console-clear-logs
Clear the MCP log cache (used by 'console-get-logs') and the Unity Editor Console window. Useful for isolating logs to a specific action by clearing the slate first.
profiler-start
Enable Unity's runtime profiler and open the Profiler window. Idempotent: calling when already enabled returns the current enabled state without error.