{"version":"2.1.299","anchor":"skillcommand-frontmatter-scrubbing-metadata-and-plugin-fiel","canonical_anchor":"skillcommand-frontmatter-scrubbing-metadata-and-plugin-fiel","heading":"Commands now record which plugin added them","tier":"internal","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/skillcommand-frontmatter-scrubbing-metadata-and-plugin-fiel","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Commands now record which plugin added them\n\nCommands now record the plugin that registered them, and stored skills keep their original header plus a note when it cannot be cleaned\n\n**Unclear.** Whether plugins can register commands in this release is not stated.\n\n**What**\n\nTwo additions:\n\n- Skills loaded from the memory store now keep a copy of their frontmatter (the settings block at the top of a skill file) exactly as written. When cleaning that block fails, they carry a note such as \"has two keys that read the same once scrubbed\" or \"could not be scrubbed\".\n\n- Commands now record which plugin registered them through `$.command.register`. Plugins are add-on packages that extend Claude Code. When a command is described with its name, arguments and plugin, sensitive arguments are hidden as `***`.\n\n**Why**\n\nClaude Code and the apps that connect to it can now show which plugin a command came from.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}