security-hook-blocks-literal-exec-eval-tokens-in-prose

The security_reminder_hook fires on literal exec( and eval( tokens anywhere in file content — including documentation, handoff docs, and skill prose describing the hook itself. This is a meta-recursion trap: writing about the hook triggers the hook. Workaround: describe the behavior using paraphrased language (‘shell execution guard’, ‘dynamic evaluation tokens’) without the exact token strings.

Related

• security-hook-blocks-exec-eval-tokens-in-prose
• security-reminder-hook-blocks-literal-exec-eval-in-prose
• destructive-hook-regex-matches-rm-inside-echo-strings
• docker
• session-close-phase-1-6-disposition-is-not-resolution
• security-hook-blocks-literal-exec-eval-in-prose
• security-hook-fires-on-literal-exec-eval-tokens-in-prose
• security-hook-triggers-on-literal-exec-eval-tokens-in-prose