What problem does it solve? Unity's runtime API does not expose programmatic control over Profiler window modules, making it impossible to toggle module visibility from code. This Skill provides honest local bookkeeping of which profiler modules are marked enabled or disabled, so related tools like profiler-get-status and profiler-list-modules can report a consistent state without pretending to control Unity internals. ## Core Features & Use Cases - Local Module State Tracking: Adds or removes a module name from the wrapper's EnabledModules set. - Input Validation: Returns an [Error] string when the module name is empty or unknown. - Use Case: While profiling a Unity game, you want to mark the GPU module as disabled in your tracking wrapper so that profiler-get-status reflects your current profiling focus, then re-enable it later with a single command. ## Quick Start Ask the AI to run the profiler-enable-module tool with moduleName set to "CPU" and enabled set to false to mark that profiler module as disabled.