godot-performance

godot-performance is a skill for Claude Code from MRCalderon3D/everything-game-dev-code. It costs 23 tokens per session (342 once invoked), scanned A, original, MIT.

A Godot profiling guide for measuring how runtime code, rendering, memory, scenes, and resources affect a game’s performance. Profiling means collecting measurements from representative game builds or scenes.

In plain words
What is it for?
Use it to investigate slow frame rates, heavy scenes, resource-loading costs, signal activity, node counts, or differences between exported platforms.
Why use it?
It replaces guesswork with measured bottlenecks and helps distinguish script, rendering, memory, and scene costs. It also supports tracking performance changes over time.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the everything-game-dev-code plugin — 74 skills, 67 commands, 42 agents, 3 hooks, 6 MCP servers shipped together

Good fit Use it to investigate slow frame rates, heavy scenes, resource-loading costs, signal activity, node counts, or differences between exported platforms.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mrcalderon3d/everything-game-dev-code/godot-performance
Install

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.

Any agent
npx skills add MRCalderon3D/everything-game-dev-code --skill godot-performance
Clone the repo
git clone --depth 1 https://github.com/MRCalderon3D/everything-game-dev-code

Made for: Claude Code.

Or install everything-game-dev-code, the plugin that ships this one along with the rest of its 74 skills, 67 commands, 42 agents, 3 hooks, 6 MCP servers.

Wrote 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.

agentmods badge for godot-performance

README.md
[![agentmods](https://agentmods.dev/badge/skills/mrcalderon3d/everything-game-dev-code/godot-performance/github.svg)](https://agentmods.dev/skills/mrcalderon3d/everything-game-dev-code/godot-performance)
Your own site
<a href="https://agentmods.dev/skills/mrcalderon3d/everything-game-dev-code/godot-performance"><img src="https://agentmods.dev/badge/skills/mrcalderon3d/everything-game-dev-code/godot-performance/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.

agentmods 80×15 button for godot-performance

Your own site · 80×15
<a href="https://agentmods.dev/skills/mrcalderon3d/everything-game-dev-code/godot-performance"><img src="https://agentmods.dev/badge/skills/mrcalderon3d/everything-game-dev-code/godot-performance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 342 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00023 $0.00342
Opus 5.5 $0.00009 $0.00137
Sonnet 5.5 $0.00005 $0.00068
Haiku 4.5 $0.00002 $0.00034

Measured 10d ago against content hash 09ab80f76fde, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

godot-performance 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.

skills/godot/godot-performance/SKILL.md · 60 lines

What it actually says

Godot Performance

Purpose

Profile Godot runtime, scene, rendering, and resource behavior based on representative builds and content.

Use When

  • performance targets are at risk
  • scene and resource complexity is rising
  • platform exports are diverging

Inputs

  • target hardware
  • representative scenes
  • current metrics
  • content and architecture assumptions

Process

  1. profile representative exported builds or representative runtime conditions
  2. separate script, rendering, memory, and scene-tree costs
  3. review signal churn, node count, resource loading, and draw behavior together
  4. prioritize changes by measured impact
  5. track baseline metrics through milestones

Outputs

  • profiling summary
  • bottleneck map
  • optimization priorities
  • baseline notes

Quality Bar

  • respects scene-tree ownership, autoload boundaries, and resource behavior
  • keeps scripts, signals, and resources understandable at scale
  • supports export reliability and content iteration without hidden coupling

Common Failure Modes

  • autoloads becoming global dumping grounds
  • signal webs with no ownership
  • shared resources causing accidental state leakage
  • godot-reviewer
  • performance-reviewer
  • technical-artist
  • godot-review
  • perf-budget
  • verify

Notes

  • Keep this skill aligned with the relevant rules layer and current project documentation.
  • If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.
Changes

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.

  1. 10d ago First seen · 60 lines · 23 tokens per session scan A 09ab80f76fde

Subscribe to this mod's changes

godot-performance is a skill published in the GitHub repository MRCalderon3D/everything-game-dev-code (96 stars, last pushed 11d ago), licensed MIT. It adds 23 tokens to every session and 342 once invoked, about $0.0001 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-10-10.

Related

Other skills, from other repositories

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.

striderZA/OpenCodeGameStudios · 38 tokens

hotfix

Emergency fix workflow that bypasses normal sprint processes with a full audit trail. Creates hotfix branch, tracks approvals, and ensures the fix is backported correctly.

striderZA/OpenCodeGameStudios · 35 tokens

cgs-bug-report

Use for bug report tasks that capture a reproducible bug with environment, steps, expected/actual behavior, severity, evidence, and owner; produce verification evidence, changed or proposed files, and handoff boundaries.

merlinhu1/codex-game-studio · 48 tokens

cgs-bug-triage

Use for bug triage tasks that classify bugs by severity, priority, reproduction confidence, owner role, risk, and release impact; produce verification evidence, changed or proposed files, and handoff boundaries.

merlinhu1/codex-game-studio · 48 tokens

cgs-bugfix

Use for bugfix tasks that fix a bounded bug with reproduction evidence, minimal change, regression coverage, and handoff notes; produce verification evidence, changed or proposed files, and handoff boundaries.

merlinhu1/codex-game-studio · 45 tokens

cgs-dev-story

Use for dev story tasks that turn a design or bug into an implementation-ready story with owner, files, acceptance tests, and dependencies; produce verification evidence, changed or proposed files, and handoff boundaries.

merlinhu1/codex-game-studio · 46 tokens