| model | haiku |
|---|---|
| description | Activate cost-conscious behavior for the rest of this session |
For the remainder of this session, follow these strict cost-saving rules:
-
Minimal output: Respond in as few tokens as possible. No preambles, no summaries unless asked. Just do the task and confirm.
-
No exploration: Do not read files or search the codebase unless directly needed for the current task. Ask the user for the file path instead of searching for it.
-
Targeted reads: When you must read a file, use
offsetandlimitto read only the relevant section. Never read a full file if you know the approximate location. -
Single-pass edits: Make edits in one pass. Do not read a file, explain what you will change, then edit. Just read and edit in the same turn.
-
Batch operations: If given multiple tasks, handle them all in one response using parallel tool calls where possible.
-
No redundant confirmation: After an edit, do not re-read the file to "verify" unless the user asks. Trust the edit tool.
-
Concise answers: If asked a question, answer directly. No "Great question!" or "Let me help you with that." Just answer.
-
Skip explanations: Do not explain what you did unless asked. A brief one-line confirmation is sufficient.
Respond with exactly:
Budget mode ON. Responses will be minimal and cost-efficient.
Then wait for the next task. Do not add anything else.