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

Kai

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,791
167 sessions · $11 each
Savings opportunity
$844
47% of spend, at list price
Practices on target
2 of 7
Focus: rtk coverage, Knowledge MCP use
Cache hit rate
72%
Team 79% · org 82%
02

Where spend could go further

FY2027 to date · estimated at list price

Savings opportunity by lever

$844 of $1,791 spend

Improve prompt caching$514Keep context lean$155Right-size models$150Route commands through rtk$24

What to change

Largest saving first

  1. Improve prompt caching$514

    Cache hit rate 72% 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. Keep context lean$155

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

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

  3. Right-size models$150

    41% of routine spend ran on Opus: code research $207 of $527, documentation $105 of $238, ops $12 of $34, presentation $37 of $78.

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

  4. Route commands through rtk$24

    62% of 1,595 Bash calls ran through rtk; 2.4M 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 Growth & SEO and the organization

PracticeKaiTeamOrgTargetRecommendation
rtk coverage62%Needs attention62%56%≥ 80% of Bash callsInstall the rtk hook so test, build, git and search commands return compact output.
Knowledge MCP use
7 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 rate72%Needs attention79%82%≥ 85% of inputKeep CLAUDE.md and tool lists stable, avoid mid-session model switches, and resume sessions instead of restarting.
Context past 100K23%Needs attention18%10%≤ 10% of inputCompact or /clear between tasks; hand broad searches to subagents so their reads stay out of the main context.
Opus on routine work41%Needs attention58%44%≤ 25% of routine spendDefault routine sessions to Sonnet and keep Opus for harness, design and hard debugging work.
Sessions using subagents49%On target47%50%≥ 30% of sessionsOn target
Tool error rate2.8%On target3.0%3.0%≤ 4% of tool callsOn target

Practices by month

Is the engineer moving toward the targets?

MonthrtkKnowledgeCacheContextModel fitSubagentsSavings opportunity
Feb 2026––45%Off target21%Needs attention62%Off target36%On target$38
Mar 2026––55%Off target21%Needs attention62%Off target41%On target$33
Apr 2026––57%Off target21%Needs attention62%Off target38%On target$65
May 202617%Off target–62%Off target24%Needs attention55%Off target54%On target$114
Jun 202645%Needs attention12%Off target62%Off target23%Needs attention53%Off target40%On target$106
Jul 202669%Needs attention24%Needs attention67%Off target22%Needs attention40%Needs attention38%On target$147
Aug 202665%Needs attention35%Needs attention72%Needs attention24%Needs attention38%Needs attention48%On target$55
Sep 202664%Needs attention39%Needs attention69%Off target24%Needs attention30%Needs attention55%On target$160
Oct 202674%Needs attention34%Needs attention78%Needs attention23%Needs attention27%Needs attention57%On target$125
04

Usage

FY2027 to date

AI spend by model

By model tier, by month

  • Opus
  • Sonnet
  • Haiku
  • Other
$0$200$400$600$61Feb$50Mar$98Apr$195May$171Jun$307Jul$128Aug$353Sep$427Oct

AI spend by session type

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

Harness$379Freeform$261Code research$527Documentation$238Ideation$276Ops$34Presentation$78

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,32624.9M113.9M8.9M3.4M$234
Opus 51,60222.6M66.4M5.7M2.3M$239
Opus 4.81,46424.6M55.4M5.1M2M$233
Opus 4.61,38833.2M54.1M5.6M2.2M$284
Opus 4.5631.9M1.8M237K100K$15
Sonnet 5.53,47835.4M169.6M13.1M5.2M$173
Sonnet 53,69350.1M143.4M12.4M4.9M$314
Sonnet 4.61,63130.2M55.8M5.5M2.4M$163
Sonnet 4.5491.5M1.4M186K88K$7
Haiku 5.55,80558.9M297.9M22.8M11.3M$17
Haiku 4.53,01045.7M120.6M10.6M4.8M$95
GPT Realtime (meetings)1252.2M5.8M510K211K$17
Total24,634331.2M1086.1M90.5M38.9M$1,791

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