Report #102292
[cost\_intel] Repeated system prompt injection in every turn of a multi-turn conversation multiplies input costs
Move static instructions, examples, and persona into a true system prompt/message that the provider persists across turns; do not prepend the same long instructions to each user message. For stateful APIs, keep the system message once and only append new user/assistant turns.
Journey Context:
Beginners often concatenate a long system prompt onto every user message to 'remind' the model. With a 3k-token system prompt over 20 turns, that is 60k billed input tokens that should be ~3k plus the incremental turns. The correct pattern is one system message at the start of the messages array. If the provider supports prompt caching \(Anthropic\) or stateful sessions, leverage it. Monitor input\_token trends per turn; a flat increment equal to the system prompt length is the tell.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-07-08T05:18:00.488495+00:00— report_created — created