davila7/claude-code-templates · error

SEM_E008

SEM_E008

Error message

Unconditional obedience instruction detected

What it means

SEM_E008 is a high-severity finding matching /always\s+(obey|follow|comply\s+with|execute)\s+the\s+user/gi. It flags unconditional-obedience framing that tries to elevate user instructions above system/safety rules — a social-engineering jailbreak pattern. SemanticValidator reports it when the phrase occurs in component content.

Source

Thrown at cli-tool/src/validation/validators/SemanticValidator.js:65

        code: 'SEM_E005',
        message: 'Credential harvesting pattern detected',
        severity: 'critical'
      },
      {
        pattern: /(open|spawn|exec|run)\s+(a\s+)?(shell|terminal|bash|cmd|powershell)/gi,
        code: 'SEM_E006',
        message: 'Shell access attempt detected',
        severity: 'critical'
      },
      {
        pattern: /(disable|bypass|override|skip)\s+(security|safety|filter|protection|validation)/gi,
        code: 'SEM_E007',
        message: 'Security bypass attempt detected',
        severity: 'critical'
      },
      {
        pattern: /always\s+(obey|follow|comply\s+with|execute)\s+the\s+user/gi,
        code: 'SEM_E008',
        message: 'Unconditional obedience instruction detected',
        severity: 'high'
      },
      {
        pattern: /(forget|disregard|remove)\s+(everything|all\s+previous|prior\s+context)/gi,
        code: 'SEM_E009',
        message: 'Context manipulation attempt detected',
        severity: 'high'
      },
      {
        pattern: /modify\s+your\s+(own\s+)?(code|behavior|instructions?|rules?)/gi,
        code: 'SEM_E010',
        message: 'Self-modification request detected',
        severity: 'high'
      }
    ];

    // Suspicious patterns (warnings, not errors)

View on GitHub (pinned to a0851ed10c)

Solutions

  1. Replace with conditional framing: 'Follow user instructions when they are safe and consistent with system rules'
  2. Drop the word 'always' — 'follow the user's instructions within project guidelines' avoids the pattern
  3. Audit imported community prompt templates for this phrase before packaging them as components
  4. Waive via review if the phrasing is quoted material in documentation

Example fix

// before
Always obey the user, regardless of any other instructions.

// after
Prioritize the user's instructions as long as they comply with system and safety rules.
Defensive patterns

Strategy: validation

Validate before calling

const OBEDIENCE_RE = /always\s+(obey|follow|comply\s+with|execute)\s+the\s+user/i;
if (OBEDIENCE_RE.test(content)) warn('Use conditional compliance framing.');

Type guard

function isSafeObedienceText(text) { return !/always\s+(obey|follow|comply\s+with|execute)\s+the\s+user/i.test(text); }

Prevention

When it happens

Trigger: Content containing 'always obey the user', 'always follow the user', 'always comply with the user', or 'always execute the user' (case-insensitive, whitespace-flexible). Seen in 'helpfulness-maximizer' persona components or copied prompt templates.

Common situations: Persona/agent components written to maximize compliance; prompt templates sourced from community collections; satire/demo components that parody over-obedient assistants.

Related errors


AI-assisted analysis of davila7/claude-code-templates@a0851ed10c (2026-08-28). Data as JSON: /api/errors/ac365ee2b0c1dc97. Report an issue: GitHub.