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

Parker

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,157
185 sessions · $12 each
Savings opportunity
$656
30% of spend, at list price
Practices on target
3 of 7
Focus: rtk coverage, Knowledge MCP use
Cache hit rate
80%
Team 78% · org 82%
02

Where spend could go further

FY2027 to date · estimated at list price

Savings opportunity by lever

$656 of $2,157 spend

Improve prompt caching$343Right-size models$227Keep context lean$68Route commands through rtk$17

What to change

Largest saving first

  1. Improve prompt caching$343

    Cache hit rate 80% 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$227

    42% of routine spend ran on Opus: code research $304 of $708, documentation $140 of $336, ops $11 of $28, presentation $95 of $241.

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

  3. Keep context lean$68

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

    61% of 1,570 Bash calls ran through rtk; 2.6M 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

PracticeParkerTeamOrgTargetRecommendation
rtk coverage61%Needs attention60%56%≥ 80% of Bash callsInstall the rtk hook so test, build, git and search commands return compact output.
Knowledge MCP use
8 findings saved back
30%Needs attention30%30%≥ 40% of sessionsSearch the knowledge MCP before re-researching a codebase, and save findings back with remember.
Cache hit rate80%Needs attention78%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 work42%Needs attention55%44%≤ 25% of routine spendDefault routine sessions to Sonnet and keep Opus for harness, design and hard debugging work.
Sessions using subagents45%On target45%50%≥ 30% of sessionsOn target
Tool error rate3.3%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––60%Off target8%On target62%Off target35%On target$24
Mar 2026––66%Off target7%On target62%Off target43%On target$93
Apr 2026––63%Off target8%On target62%Off target33%On target$80
May 202628%Off target–73%Needs attention11%Needs attention55%Off target44%On target$113
Jun 202641%Needs attention8%Off target73%Needs attention8%On target53%Off target38%On target$98
Jul 202674%Needs attention19%Needs attention77%Needs attention7%On target40%Needs attention43%On target$51
Aug 202667%Needs attention40%On target78%Needs attention11%Needs attention38%Needs attention41%On target$107
Sep 202665%Needs attention38%Needs attention87%On target6%On target30%Needs attention50%On target$43
Oct 202669%Needs attention33%Needs attention84%Needs attention11%Needs attention27%Needs attention58%On target$47
04

Usage

FY2027 to date

AI spend by model

By model tier, by month

  • Opus
  • Sonnet
  • Haiku
  • Other
$0$100$200$300$400$51Feb$202Mar$148Apr$279May$253Jun$171Jul$352Aug$333Sep$367Oct

AI spend by session type

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

Harness$384Freeform$271Code research$708Documentation$336Ideation$189Ops$28Presentation$241

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,14411.7M107.7M7.6M3.4M$175
Opus 52,38518.1M115M8.5M3.3M$284
Opus 4.81,64819M72.3M5.8M2.4M$228
Opus 4.63,13648.4M127.9M11.3M4.3M$485
Opus 4.5581.4M2.4M240K90K$12
Sonnet 5.54,11823.7M214.3M15.2M6.3M$170
Sonnet 55,90239M267.7M19.6M8.3M$396
Sonnet 4.62,79137.6M112.8M9.6M4.1M$245
Sonnet 4.5491.1M2M195K66K$6
Haiku 5.56,89741.2M363M25.8M12.7M$17
Haiku 4.55,08146M239.5M18.2M7.3M$129
GPT Realtime (meetings)1051.3M5M402K162K$11
Total34,314288.6M1629.5M122.4M52.6M$2,157

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