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

Lane

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,410
139 sessions · $10 each
Savings opportunity
$324
23% of spend, at list price
Practices on target
4 of 7
Focus: rtk coverage, Knowledge MCP use
Cache hit rate
86%
Team 79% · org 82%
02

Where spend could go further

FY2027 to date · estimated at list price

Savings opportunity by lever

$324 of $1,410 spend

Improve prompt caching$163Right-size models$111Keep context lean$36Route commands through rtk$15

What to change

Largest saving first

  1. Improve prompt caching$163

    Cache hit rate 86% 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$111

    38% of routine spend ran on Opus: code research $135 of $369, documentation $87 of $216, ops $6 of $19, presentation $35 of $79.

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

  3. Keep context lean$36

    7% 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

    66% of 1,282 Bash calls ran through rtk; 1.8M 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

PracticeLaneTeamOrgTargetRecommendation
rtk coverage66%Needs attention62%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
29%Needs attention30%30%≥ 40% of sessionsSearch the knowledge MCP before re-researching a codebase, and save findings back with remember.
Cache hit rate86%On target79%82%≥ 85% of inputOn target
Context past 100K7%On target18%10%≤ 10% of inputOn target
Opus on routine work38%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 rate3.3%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––64%Off target10%Needs attention–19%Needs attention$5
Mar 2026––62%Off target8%On target62%Off target46%On target$17
Apr 2026––67%Off target7%On target62%Off target28%Needs attention$21
May 202617%Off target–70%Needs attention7%On target55%Off target34%On target$20
Jun 202643%Needs attention13%Off target71%Needs attention10%Needs attention53%Off target39%On target$82
Jul 202674%Needs attention27%Needs attention76%Needs attention6%On target40%Needs attention46%On target$87
Aug 202667%Needs attention31%Needs attention84%Needs attention9%On target38%Needs attention47%On target$22
Sep 202675%Needs attention34%Needs attention82%Needs attention9%On target30%Needs attention59%On target$37
Oct 202675%Needs attention35%Needs attention91%On target6%On target27%Needs attention59%On target$32
04

Usage

FY2027 to date

AI spend by model

By model tier, by month

  • Opus
  • Sonnet
  • Haiku
  • Other
$0$100$200$300$400$12Feb$31Mar$50Apr$50May$191Jun$290Jul$163Aug$235Sep$388Oct

AI spend by session type

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

Harness$235Freeform$265Code research$369Documentation$216Ideation$227Ops$19Presentation$79

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,8006.7M146.2M9.8M4.2M$190
Opus 51,91012.6M93.4M6.8M2.7M$220
Opus 4.81,58619.9M72.8M5.9M2.6M$239
Opus 4.680611.8M30.3M2.7M1.1M$119
Opus 4.517336K701K66K25K$3
Sonnet 5.54,4199.9M267M17.7M7.1M$161
Sonnet 53,73827.9M184.5M13.6M5.5M$273
Sonnet 4.61,16915.9M48.2M4.1M1.7M$104
Sonnet 4.511189K395K37K16K$1
Haiku 5.59,07815.7M483M31.8M15.3M$18
Haiku 4.52,97021.7M136.2M10.1M4.3M$69
GPT Realtime (meetings)164950K8.2M582K263K$14
Total28,668143.4M1471M103M45M$1,410

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