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

Wren

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,929
130 sessions · $15 each
Savings opportunity
$497
26% of spend, at list price
Practices on target
3 of 7
Focus: rtk coverage, Knowledge MCP use
Cache hit rate
82%
Team 84% · org 82%
02

Where spend could go further

FY2027 to date · estimated at list price

Savings opportunity by lever

$497 of $1,929 spend

Improve prompt caching$252Right-size models$173Keep context lean$59Route commands through rtk$14

What to change

Largest saving first

  1. Improve prompt caching$252

    Cache hit rate 82% 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$173

    41% of routine spend ran on Opus: code research $130 of $300, documentation $24 of $78, ops $262 of $637, presentation $4 of $14.

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

  3. Keep context lean$59

    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$14

    64% of 1,268 Bash calls ran through rtk; 2M 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

PracticeWrenTeamOrgTargetRecommendation
rtk coverage64%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 rate82%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 100K9%On target6%10%≤ 10% of inputOn target
Opus on routine work41%Needs attention33%44%≤ 25% of routine spendDefault routine sessions to Sonnet and keep Opus for harness, design and hard debugging work.
Sessions using subagents47%On target51%50%≥ 30% of sessionsOn target
Tool error rate3.4%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––61%Off target7%On target62%Off target37%On target$36
Mar 2026––67%Off target9%On target62%Off target33%On target$18
Apr 2026––67%Off target11%Needs attention62%Off target26%Needs attention$46
May 202622%Off target–73%Needs attention11%Needs attention55%Off target48%On target$44
Jun 202647%Needs attention13%Off target77%Needs attention8%On target53%Off target47%On target$95
Jul 202675%Needs attention24%Needs attention75%Needs attention7%On target40%Needs attention40%On target$82
Aug 202672%Needs attention35%Needs attention77%Needs attention9%On target38%Needs attention47%On target$108
Sep 202672%Needs attention33%Needs attention85%On target9%On target30%Needs attention49%On target$47
Oct 202667%Needs attention37%Needs attention90%On target9%On target27%Needs attention63%On target$21
04

Usage

FY2027 to date

AI spend by model

By model tier, by month

  • Opus
  • Sonnet
  • Haiku
  • Other
$0$200$400$600$72Feb$35Mar$91Apr$108May$301Jun$248Jul$385Aug$457Sep$231Oct

AI spend by session type

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

Harness$514Freeform$360Code research$300Documentation$78Ideation$26Ops$637Presentation$14

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,4156.8M117.3M7.9M3.1M$152
Opus 53,01624.4M153.1M11.3M4.6M$385
Opus 4.81,89423.2M97.9M7.7M3.2M$293
Opus 4.61,53422M62.1M5.4M2.2M$229
Opus 4.5901.8M3.2M320K158K$16
Sonnet 5.53,1538.9M179.9M12M5M$115
Sonnet 56,48050.1M314.9M23.3M8.6M$461
Sonnet 4.62,09024.3M88.4M7.2M2.7M$167
Sonnet 4.5901.9M3.5M347K143K$10
Haiku 5.54,3308.4M212.6M14.1M5.9M$8
Haiku 4.53,95930.9M170.1M12.8M5.4M$91
GPT Realtime (meetings)2680K1.2M79K29K$2
Total29,077202.8M1404.3M102.6M41M$1,929

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