How this model works

This estimator gives a quick approximation of what your tooling budget should be. Most teams have a mixture of different types of tasks, our calculator has been benchmarked against some real-world team usage averages. Your mileage will vary, and I am not the one paying your token bills, so please calibrate this against your team usage patterns. Estimates based on publicly available pricing information; individual codebase and developer usage patterns will vary.

Input token counts are scaled by codebase size. The baseline values above correspond to a 1M-line codebase — roughly an agentic session reading 20–40 files per task. Generally, input tokens scale up and down with the codebase size, since we need to read more to get sufficient context for a safe change. Output tokens do not scale with codebase size.

These are estimates. Real costs depend on actual context sizes, session lengths, model routing decisions, and whether your team's usage stays within included credit pools. The model is intentionally transparent so you can adjust assumptions to match your team.

Cost should not be the only steer on tool choice. For a full discussion of other factors affecting choice of tool GitHub Copilot vs Claude Code vs Cursor.

← Blog