{"version":"2.1.301","anchor":"mod-authoring-follow-up-note-after-a-mod-command-runs","canonical_anchor":"mod-authoring-follow-up-note-after-a-mod-command-runs","heading":"Claude gives a short reply after you run a command from a mod you are building","tier":"notice","area":"Mods","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/mod-authoring-follow-up-note-after-a-mod-command-runs","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### Claude gives a short reply after you run a command from a mod you are building\n\nAfter you run a command from a mod you are building, Claude now replies in a line or two and may offer the plugin-authoring skill\n\n**What**\n\nWhen you run a command that belongs to a mod (an add-on) you are building, Claude Code now sends Claude a one-time note. The note tells Claude to:\n\n- Reply in one or two lines\n\n- Use no tools\n\n- Offer the plugin-authoring skill in one line if the output shows the mod worked\n\n**Why**\n\nPeople building plugins get a short response after testing a command, plus a pointer to the plugin-authoring skill when things go well.\n\n- Area: Mods\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}