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

Logan

Lead 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,651
206 sessions · $13 each
Savings opportunity
$569
21% of spend, at list price
Practices on target
3 of 7
Focus: rtk coverage, Knowledge MCP use
Cache hit rate
82%
Team 79% · org 82%
02

Where spend could go further

FY2027 to date · estimated at list price

Savings opportunity by lever

$569 of $2,651 spend

Improve prompt caching$343Right-size models$134Keep context lean$73Route commands through rtk$19

What to change

Largest saving first

  1. Improve prompt caching$343

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

    41% of routine spend ran on Opus: code research $186 of $440, documentation $82 of $226, ops $32 of $75, presentation $21 of $50.

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

  3. Keep context lean$73

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

    63% of 2,018 Bash calls ran through rtk; 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 Web Platform and the organization

PracticeLoganTeamOrgTargetRecommendation
rtk coverage63%Needs attention46%56%≥ 80% of Bash callsInstall the rtk hook so test, build, git and search commands return compact output.
Knowledge MCP use
6 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 rate82%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 100K8%On target8%10%≤ 10% of inputOn target
Opus on routine work41%Needs attention42%44%≤ 25% of routine spendDefault routine sessions to Sonnet and keep Opus for harness, design and hard debugging work.
Sessions using subagents51%On target51%50%≥ 30% of sessionsOn target
Tool error rate2.6%On target2.7%3.0%≤ 4% of tool callsOn target

Practices by month

Is the engineer moving toward the targets?

MonthrtkKnowledgeCacheContextModel fitSubagentsSavings opportunity
Feb 2026––61%Off target9%On target62%Off target39%On target$45
Mar 2026––67%Off target9%On target62%Off target30%On target$49
Apr 2026––68%Off target6%On target62%Off target51%On target$81
May 202622%Off target–68%Off target6%On target55%Off target36%On target$120
Jun 202641%Needs attention17%Needs attention74%Needs attention8%On target53%Off target52%On target$88
Jul 202675%Needs attention19%Needs attention75%Needs attention7%On target40%Needs attention49%On target$70
Aug 202669%Needs attention37%Needs attention83%Needs attention9%On target38%Needs attention49%On target$40
Sep 202669%Needs attention36%Needs attention88%On target7%On target30%Needs attention59%On target$28
Oct 202671%Needs attention32%Needs attention86%On target10%On target27%Needs attention61%On target$46
04

Usage

FY2027 to date

AI spend by model

By model tier, by month

  • Opus
  • Sonnet
  • Haiku
  • Other
$0$200$400$600$800$94Feb$140Mar$231Apr$282May$252Jun$240Jul$396Aug$364Sep$652Oct

AI spend by session type

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

Harness$840Freeform$925Code research$440Documentation$226Ideation$96Ops$75Presentation$50

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.55,30023.2M259.2M18M6.6M$367
Opus 54,38721.5M196.3M13.9M6M$443
Opus 4.82,24223.5M91.5M7.3M2.9M$281
Opus 4.63,60057.4M144.6M12.9M5.4M$576
Opus 4.51392.6M4.7M465K172K$22
Sonnet 5.56,41628.6M314.1M21.9M10.2M$246
Sonnet 55,41032.3M278.4M19.8M8.2M$377
Sonnet 4.62,38933.8M98.4M8.4M3.4M$214
Sonnet 4.5971.9M3.6M352K159K$11
Haiku 5.59,17143.2M464.7M32.4M13.5M$20
Haiku 4.53,84529.6M174.4M13M5.2M$90
GPT Realtime (meetings)54632K2.6M204K85K$6
Total43,050298.3M2032.3M148.8M61.9M$2,651

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