{"version":"2.1.299","anchor":"plugin-commandsskills-keep-as-written-frontmatter-and-fall","canonical_anchor":"plugin-commandsskills-keep-as-written-frontmatter-and-fall","heading":"Plugin commands with unsafe allowed-tools now get none, with a warning","tier":"notice","area":"Plugins","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/plugin-commandsskills-keep-as-written-frontmatter-and-fall","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Plugin commands with unsafe allowed-tools now get none, with a warning\n\nA plugin command whose `allowed-tools` are too long or name a folder holding a variable or `$` now has them left empty, with a warning\n\n**What**\n\nThe same caution now covers plugin commands. A command's `allowed-tools` field lists tools it may use without asking you. For a command from a plugin (an add-on package), Claude Code now leaves that list empty and shows a warning when the entries:\n\n- are too long\n\n- name a folder that holds a variable or a `$`\n\nThe warning says its allowed-tools \"are not filled in\". Claude Code also now keeps a plugin command's or skill's frontmatter (the settings block at the top of its file) exactly as written, alongside the version it reads.\n\n**Why**\n\nA malformed plugin command can no longer end up allowed to use the wrong tools.\n\n- Area: Plugins\n- Names: `allowed-tools`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}