{"version":"2.1.284","anchor":"hooks-module-validation-reports-hooks-telemetry-declarations","canonical_anchor":"hooks-module-validation-reports-hooks-telemetry-declarations","heading":"Plugin hooks-module checks now report their usage-data declarations","tier":"internal","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/hooks-module-validation-reports-hooks-telemetry-declarations","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Plugin hooks-module checks now report their usage-data declarations\n\nChecking a plugin hooks module now lists what it declares for usage data and can report problems for that module\n\n**Unclear.** What the checks look for, and what counts as a problem, is not clear.\n\n**What**\n\nWhen Claude Code checks a plugin's hooks module, it now lists what the module declares for hooks telemetry, meaning the usage data its hooks send. Hooks are commands a plugin runs at set points. The check can also report a problem under that module's own name.\n\n**Why**\n\nThis is part of a plugin hooks-module system that is not yet documented.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}