Thinksy EngineeringEngineer usage detail
FY2027 · Feb 2026 – Jan 2027Data through Oct 2026
← Engineering Effectiveness report
Data & Analytics · Sam Okafor

Quinn

Engineer · AI usage, harness practices and where spend could have gone further.

Demonstration report. This engineer and their usage are synthetic.

This page is for the engineer and their manager to find cheaper defaults and harness fixes. It is never used to rank people.

Period
01

Summary

FY2027 to date

AI spend
$1,612
141 sessions · $11 each
Savings opportunity
$965
60% of spend, at list price
Practices on target
3 of 7
Focus: Cache hit rate, Opus on routine work
Cache hit rate
66%
Team 78% · org 82%
02

Where spend could go further

FY2027 to date · estimated at list price

Savings opportunity by lever

$965 of $1,612 spend

Improve prompt caching$536Right-size models$351Keep context lean$56Route commands through rtk$22

What to change

Largest saving first

  1. Improve prompt caching$536

    Cache hit rate 66% against an 85% target.

    Keep stable context at the front of prompts and avoid switching models mid-session, so 85% of input reads from cache.

  2. Right-size models$351

    82% of routine spend ran on Opus: code research $501 of $605, documentation $204 of $249, ops $26 of $32, presentation $106 of $130.

    Run docs, decks, ops and read-only research on Sonnet instead of Opus.

  3. Keep context lean$56

    9% of input tokens were past 100K of context.

    Compact or /clear between tasks instead of carrying more than 100K tokens of context.

  4. Route commands through rtk$22

    65% of 1,296 Bash calls ran through rtk; 1.8M tokens of command output went into context.

    rtk compacts test, build, git and search output before it reaches the model (about 70% smaller).

03

Harness practices

Compared with Data & Analytics and the organization

PracticeQuinnTeamOrgTargetRecommendation
rtk coverage65%Needs attention60%56%≥ 80% of Bash callsInstall the rtk hook so test, build, git and search commands return compact output.
Knowledge MCP use
5 findings saved back
31%Needs attention30%30%≥ 40% of sessionsSearch the knowledge MCP before re-researching a codebase, and save findings back with remember.
Cache hit rate66%Off target78%82%≥ 85% of inputKeep CLAUDE.md and tool lists stable, avoid mid-session model switches, and resume sessions instead of restarting.
Context past 100K9%On target8%10%≤ 10% of inputOn target
Opus on routine work82%Off target55%44%≤ 25% of routine spendDefault routine sessions to Sonnet and keep Opus for harness, design and hard debugging work.
Sessions using subagents49%On target45%50%≥ 30% of sessionsOn target
Tool error rate2.9%On target3.4%3.0%≤ 4% of tool callsOn target

Practices by month

Is the engineer moving toward the targets?

MonthrtkKnowledgeCacheContextModel fitSubagentsSavings opportunity
Feb 2026––45%Off target6%On target88%Off target26%Needs attention$20
Mar 2026––52%Off target10%On target88%Off target31%On target$39
Apr 2026––51%Off target9%On target88%Off target35%On target$35
May 202629%Off target–53%Off target10%On target86%Off target39%On target$84
Jun 202652%Needs attention17%Needs attention61%Off target10%On target86%Off target45%On target$181
Jul 202676%Needs attention23%Needs attention63%Off target11%Needs attention82%Off target40%On target$137
Aug 202670%Needs attention36%Needs attention68%Off target10%On target81%Off target55%On target$226
Sep 202664%Needs attention31%Needs attention71%Needs attention7%On target79%Off target61%On target$71
Oct 202672%Needs attention39%Needs attention71%Needs attention7%On target79%Off target53%On target$172
04

Usage

FY2027 to date

AI spend by model

By model tier, by month

  • Opus
  • Sonnet
  • Haiku
  • Other
$0$200$400$600$32Feb$54Mar$53Apr$109May$284Jun$206Jul$437Aug$143Sep$293Oct

AI spend by session type

Routine types (documentation, presentation, ops, code research) rarely need Opus

Harness$243Freeform$224Code research$605Documentation$249Ideation$129Ops$32Presentation$130

Tokens by model

Cache reads are billed at a fraction of uncached input; a high share is what good caching looks like

ModelRequestsUncached inputCache readsCache writesOutputSpend
Opus 5.52,31430.7M92.6M7.9M3.4M$249
Opus 53,41249.4M129.5M11.4M4.6M$499
Opus 4.82,11440.2M78.2M7.6M3.3M$369
Opus 4.61,27030.2M39.7M4.5M1.9M$245
Opus 4.5381.2M1.1M144K66K$9
Sonnet 5.570910.2M30.7M2.6M1.1M$41
Sonnet 51,19817.4M43.9M3.9M1.5M$103
Sonnet 4.641510M16.3M1.7M714K$52
Sonnet 4.59330K306K41K14K$1
Haiku 5.51,48622.6M68.2M5.8M2.6M$5
Haiku 4.597816.4M35.6M3.3M1.4M$31
GPT Realtime (meetings)561.1M2.1M207K100K$8
Total13,999229.8M538.3M49M20.7M$1,612

Methodology

  • Spend and tokens come from LiteLLM gateway logs and imported agent session history, priced at API list rates.
  • Savings are estimates: routine Opus work repriced at the Sonnet available at the time; uncached input moved to cache reads up to an 85% hit rate; rtk removing 70% of unfiltered command output, which stays in context for about half the session's remaining turns; and 50% of input past 100K context avoided by compacting. Levers overlap, so the total is an upper bound.
  • rtk and the knowledge MCP are scored from their rollout (rtk May 2026, knowledge MCP Jun 2026).
  • Generated Oct 20, 2026, 7:46 AM.
Engineer Usage Detail (demo) · Thomas Tucker