jbaruch/koog
Koog 1.0 idioms, gotchas, and scaffolding skills for Kotlin agents on the JVM
86
88%
Does it follow best practices?
Impact
86%
1.86xAverage score across 45 eval scenarios
Advisory
Suggest reviewing before use
task.mdevals/scenario-18/
Cache a Long System Prompt for Anthropic Calls
Problem/Feature Description
A developer runs a Koog 1.0 agent against Anthropic Opus. The agent has a multi-thousand-word system prompt full of domain instructions, style guides, and examples. It's invoked frequently (~10× per minute) and they're seeing high token bills — most of which is the system prompt being re-billed on every call.
They want to mark the system prompt as cacheable so subsequent calls within Anthropic's TTL hit the cache and pay the reduced rate. They asked specifically about how to set the cache breakpoint.
Output Specification
Walk through how to mark the prompt as cacheable. Produce the prompt definition as a single Kotlin snippet, labeled.
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10
scenario-11
scenario-12
scenario-13
scenario-14
scenario-15
scenario-16
scenario-17
scenario-18
scenario-19
scenario-20
scenario-21
scenario-22
scenario-23
scenario-24
scenario-25
scenario-26
scenario-27
scenario-28
scenario-29
scenario-30
scenario-31
scenario-32
scenario-33
scenario-34
scenario-35
scenario-36
scenario-37
scenario-38
scenario-39
scenario-40
scenario-41
scenario-42
scenario-43
scenario-44
scenario-45
skills
add-observability
add-persistence
add-rag
add-structured-output
add-token-budgeting
add-tool
cache-llm-calls
define-prompt
domain-model-subtask-pipeline
references
enable-prompt-caching
handle-agent-events
manage-state
migrate-from-0-x
model-planner-subtasks
persist-chat-history
query-sql-from-agent
scaffold-agent
snapshot-and-restore
test-koog-agents
trace-agent-internals
use-attachments
use-functional-agent
use-llm-node-variants
use-planner
wire-a2a
wire-acp-server
wire-ktor-server
wire-mcp-server
wire-spring-boot