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

The security_reminder_hook regex triggers on literal exec( and eval( tokens even in prose documentation, handoff files, and comments describing the hook itself. This is a known meta-recursion issue — any file that documents the hook pattern by example will be blocked. Workaround: use descriptive language instead of literal tokens (e.g., ‘the exec-family functions’ or ‘dynamic evaluation calls’).

Related

• security-reminder-hook-blocks-literal-exec-eval-in-prose
• hook-regex-cmd-start-not-backup-anchors-required
• hook-regex-false-positives-require-cmd-start-not-backup-anch
• session-close-phase-1-6-disposition-is-not-resolution
• stop-hook-blocks-pure-planning-sessions-pathological-loop
• security-hook-blocks-literal-exec-eval-tokens-in-prose
• 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
• integration-test-passwords-flag-secret-scanner