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 dcc-mcp/dcc-mcp-godot --skill godot-inputgit clone --depth 1 https://github.com/dcc-mcp/dcc-mcp-godotWrote 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/dcc-mcp/dcc-mcp-godot/godot-input)<a href="https://agentmods.dev/skills/dcc-mcp/dcc-mcp-godot/godot-input"><img src="https://agentmods.dev/badge/skills/dcc-mcp/dcc-mcp-godot/godot-input/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/dcc-mcp/dcc-mcp-godot/godot-input"><img src="https://agentmods.dev/badge/skills/dcc-mcp/dcc-mcp-godot/godot-input.svg" alt="Reviewed on agentmods" width="80" 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.00079 | $0.00540 |
| Opus 5.5 | $0.00032 | $0.00216 |
| Sonnet 5.5 | $0.00016 | $0.00108 |
| Haiku 4.5 | $0.00008 | $0.00054 |
Grade A, and why
godot-input 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.
What it actually says
Godot Input
Use these editor-integrated tools after opening the target Godot project. Paths must remain under res://.
set_input_action defaults to persist: false: it edits only the editor process InputMap, does not save, and does not rebind a running game. Use persist: true to author one input/<action> project default. This mode reads the project's existing events, never copies editor shortcuts, and leaves the editor InputMap unchanged. ProjectSettings.save() saves the whole current project configuration, including other unsaved settings. Save failures restore the target in-memory setting and return an error; disk rollback is not guaranteed. Start/restart the game to load saved defaults. Use get_input_actions with source: project to inspect project settings; the default source: editor preserves the legacy view (excluding ui_ actions). Project queries include built-in UI actions. Events are human-readable strings, not round-trip event payloads.
The setter authors one logical keycode only. Existing mouse, joypad, physical key, modifier and device bindings remain intact unless replace_events: true explicitly clears all events. Omitting keycode adds nothing; replacement without it clears the action. Omitting deadzone preserves it, or uses 0.5 for a new action; existing settings without it use the native 0.2 default. Null event entries are preserved (shown as empty placeholders by the getter). events, button, and simulation parameters are not accepted by this setter; they do not describe an implemented event-authoring API. Use simulation tools for the running game, not for project persistence.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +4 lines · +8 tokens per session 63ee96ae422f
- 1mo ago First seen · 21 lines · 71 tokens per session scan A f2d04f93d9a0
godot-input is a skill published in the GitHub repository dcc-mcp/dcc-mcp-godot (3 stars, last pushed yesterday), licensed MIT. It adds 79 tokens to every session and 540 once invoked, about $0.0003 per session on Opus 5.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
qa-plan
Generate a QA test plan for a sprint or feature. Reads GDDs and story files, classifies stories by test type (Logic/Integration/Visual/UI), and produces a structured test plan covering automated tests required, manual test cases, smoke test scope, and playtest sign-off requirements. Run before sprint begins or when…
asset-audit
Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard violations.
balance-check
Analyzes game balance data files, formulas, and configuration to identify outliers, broken progressions, degenerate strategies, and economy imbalances. Use after modifying any balance-related data or design. Use when user says 'balance report', 'check game balance', 'run a balance check'.
code-review
Performs an architectural and quality code review on a specified file or set of files. Checks for coding standard compliance, architectural pattern adherence, SOLID principles, testability, and performance concerns.
hybrid-prototype
Fast-lane prototype skill for the hybrid workflow. Builds a playable prototype in 2-3 days with minimal process overhead. Designed for discovery phase.
milestone-review
Generates a comprehensive milestone progress review including feature completeness, quality metrics, risk assessment, and go/no-go recommendation. Use at milestone checkpoints or when evaluating readiness for a milestone deadline.