home/writing/prompt-conflicting-injected-input

Prompt Conflicting Injected Input

GPTClaudeGemini··▲ 231 copies·updated 2026-07-14

prompt-conflicting-injected-input.prompt

---
title: prompt.conflicting_injected_input
---

## What it checks

Crux emits this finding when multiple injected sources contribute the same prompt input field with obviously incompatible JSON Schema fragments.

## Why it matters

Conflicting injected schemas make the effective prompt contract ambiguous. Validation, replay, eval authoring, and devtools forms can disagree about what the field should contain.

## How to fix

Rename one field, make the contributed schemas compatible, or move the shared field into the prompt input schema so every injected source agrees on one contract.

## When to suppress

Suppress only when the conflict is a known false positive and another boundary normalizes the value before prompt execution:

when to use it

Community prompt sourced from the open-source GitHub repo use-crux/crux (Apache-2.0). A "Prompt Conflicting Injected Input" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.