Thinksy EngineeringEngineer usage detail
FY2027 · Feb 2026 – Jan 2027Data through Oct 2026
← Engineering Effectiveness report
Infrastructure · Robin Silva

Tatum

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
$2,485
159 sessions · $16 each
Savings opportunity
$770
31% of spend, at list price
Practices on target
3 of 7
Focus: rtk coverage, Knowledge MCP use
Cache hit rate
79%
Team 84% · org 82%
02

Where spend could go further

FY2027 to date · estimated at list price

Savings opportunity by lever

$770 of $2,485 spend

Improve prompt caching$435Right-size models$248Keep context lean$72Route commands through rtk$15

What to change

Largest saving first

  1. Improve prompt caching$435

    Cache hit rate 79% 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$248

    43% of routine spend ran on Opus: code research $159 of $359, documentation $113 of $265, ops $318 of $752, presentation $10 of $29.

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

  3. Keep context lean$72

    8% 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$15

    63% of 1,562 Bash calls ran through rtk; 2.3M 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 Infrastructure and the organization

PracticeTatumTeamOrgTargetRecommendation
rtk coverage63%Needs attention69%56%≥ 80% of Bash callsInstall the rtk hook so test, build, git and search commands return compact output.
Knowledge MCP use
4 findings saved back
28%Needs attention37%30%≥ 40% of sessionsSearch the knowledge MCP before re-researching a codebase, and save findings back with remember.
Cache hit rate79%Needs attention84%82%≥ 85% of inputKeep CLAUDE.md and tool lists stable, avoid mid-session model switches, and resume sessions instead of restarting.
Context past 100K8%On target6%10%≤ 10% of inputOn target
Opus on routine work43%Needs attention33%44%≤ 25% of routine spendDefault routine sessions to Sonnet and keep Opus for harness, design and hard debugging work.
Sessions using subagents52%On target51%50%≥ 30% of sessionsOn target
Tool error rate3.2%On target3.1%3.0%≤ 4% of tool callsOn target

Practices by month

Is the engineer moving toward the targets?

MonthrtkKnowledgeCacheContextModel fitSubagentsSavings opportunity
Feb 2026––58%Off target9%On target62%Off target42%On target$49
Mar 2026––62%Off target7%On target62%Off target24%Needs attention$71
Apr 2026––66%Off target8%On target62%Off target34%On target$86
May 202624%Off target–72%Needs attention10%On target55%Off target40%On target$106
Jun 202649%Needs attention10%Off target70%Needs attention6%On target53%Off target57%On target$148
Jul 202674%Needs attention22%Needs attention74%Needs attention9%On target40%Needs attention60%On target$130
Aug 202675%Needs attention32%Needs attention79%Needs attention11%Needs attention38%Needs attention55%On target$61
Sep 202666%Needs attention31%Needs attention82%Needs attention8%On target30%Needs attention61%On target$82
Oct 202670%Needs attention38%Needs attention87%On target7%On target27%Needs attention54%On target$38
04

Usage

FY2027 to date

AI spend by model

By model tier, by month

  • Opus
  • Sonnet
  • Haiku
  • Other
$0$200$400$600$96Feb$128Mar$186Apr$260May$364Jun$370Jul$248Aug$479Sep$353Oct

AI spend by session type

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

Harness$592Freeform$403Code research$359Documentation$265Ideation$85Ops$752Presentation$29

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,64012M126.7M8.9M3.4M$187
Opus 52,80722.9M134.5M10M3.9M$342
Opus 4.82,48033.5M110.3M9.2M3.8M$375
Opus 4.62,94746.1M115.5M10.3M4.9M$475
Opus 4.51282.5M4.1M425K202K$22
Sonnet 5.54,31922.2M256.4M17.8M6.9M$183
Sonnet 56,16552.6M293.8M22.1M9M$463
Sonnet 4.63,36746.6M131.6M11.4M4.9M$295
Sonnet 4.51412.6M4.2M429K156K$13
Haiku 5.56,03421.4M268.4M18.5M9.4M$12
Haiku 4.54,12243.1M193.4M15.1M6.2M$112
GPT Realtime (meetings)56592K2.1M172K76K$5
Total35,206306.1M1641.1M124.3M52.8M$2,485

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