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

Marlo

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,284
169 sessions · $14 each
Savings opportunity
$543
24% 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

$543 of $2,284 spend

Improve prompt caching$300Right-size models$156Keep context lean$70Route commands through rtk$17

What to change

Largest saving first

  1. Improve prompt caching$300

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

    44% of routine spend ran on Opus: code research $200 of $462, documentation $85 of $191, ops $68 of $152, presentation $27 of $65.

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

  3. Keep context lean$70

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

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

PracticeMarloTeamOrgTargetRecommendation
rtk coverage64%Needs attention46%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
32%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 work44%Needs attention42%44%≤ 25% of routine spendDefault routine sessions to Sonnet and keep Opus for harness, design and hard debugging work.
Sessions using subagents49%On target51%50%≥ 30% of sessionsOn target
Tool error rate3.0%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––60%Off target6%On target62%Off target18%Needs attention$53
Mar 2026––66%Off target9%On target62%Off target34%On target$46
Apr 2026––67%Off target10%Needs attention62%Off target31%On target$80
May 202629%Off target–72%Needs attention8%On target55%Off target35%On target$112
Jun 202642%Needs attention16%Needs attention74%Needs attention10%Needs attention53%Off target50%On target$68
Jul 202666%Needs attention27%Needs attention80%Needs attention10%Needs attention40%Needs attention48%On target$61
Aug 202673%Needs attention38%Needs attention81%Needs attention9%On target38%Needs attention58%On target$67
Sep 202675%Needs attention37%Needs attention86%On target10%On target30%Needs attention55%On target$37
Oct 202674%Needs attention31%Needs attention88%On target6%On target27%Needs attention65%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$119Feb$106Mar$173Apr$270May$209Jun$253Jul$384Aug$463Sep$307Oct

AI spend by session type

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

Harness$450Freeform$804Code research$462Documentation$191Ideation$160Ops$152Presentation$65

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.53,30111M149.2M10.2M4.1M$208
Opus 54,26224.8M190.3M13.7M5.7M$448
Opus 4.82,00819.6M87.5M6.8M2.9M$257
Opus 4.63,05845.9M121.8M10.7M4.6M$472
Opus 4.51623.3M5.9M584K228K$29
Sonnet 5.53,84113.1M190.9M13M5.3M$131
Sonnet 55,95537M283.5M20.5M8.7M$403
Sonnet 4.62,20331.2M97.6M8.2M3.5M$206
Sonnet 4.51302.7M4.7M472K199K$14
Haiku 5.54,82616.5M256.9M17.4M7.1M$10
Haiku 4.54,16733.3M188.2M14.1M5.4M$97
GPT Realtime (meetings)104819K5.3M391K165K$10
Total34,017239.1M1581.8M116.2M47.9M$2,284

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