1.4 KiB
1.4 KiB
Usage and Token Budgeting
How Tokens Are Spent
Tokens are consumed based on input length, output length, and tool usage. Long prompts and repeated context increase usage quickly.
Best Practices to Reduce Usage
- Use clear, bounded requests with specific goals.
- Prefer targeted edits over full rewrites.
- Reuse context by referencing earlier outputs instead of re-pasting.
- Ask for summaries before requesting changes.
Examples of Efficient Prompts
- "Summarize this file in 5 bullets. Then propose a refactor plan."
- "Update only the functions in this file that handle validation."
- "List risks in this change and suggest tests to add."
Daily and Monthly Budgeting Tips
- Batch related questions in a single prompt.
- Timebox explorations and stop when enough info is gathered.
- Avoid repeated retries without changing the prompt.
Budgeting Routine
- Start with a plan-first request for large tasks.
- Limit each request to one output type.
- End sessions with a short summary for easy follow-up.
Red Flags That Burn Tokens Quickly
- Large file pastes with no clear ask.
- Multiple full rewrites in one session.
- Repeated "start over" requests.
Team Habits That Help
- Capture reusable prompts in a shared doc.
- Standardize request templates.
- Agree on when to use agents vs chat.
Quick Checklist
- Is the request specific and scoped?
- Do I need the whole file or just a section?
- Can I ask for a plan first?