Thinksy EngineeringEngineer usage detail
FY2027 · Feb 2026 – Jan 2027Data through Oct 2026
← Engineering Effectiveness report
Content Pipeline · Jamie Park

Blake

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,030
184 sessions · $11 each
Savings opportunity
$654
32% of spend, at list price
Practices on target
3 of 7
Focus: Opus on routine work, rtk coverage
Cache hit rate
77%
Team 82% · org 82%
02

Where spend could go further

FY2027 to date · estimated at list price

Savings opportunity by lever

$654 of $2,030 spend

Improve prompt caching$358Right-size models$212Keep context lean$62Route commands through rtk$23

What to change

Largest saving first

  1. Improve prompt caching$358

    Cache hit rate 77% 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$212

    88% of routine spend ran on Opus: code research $313 of $351, documentation $146 of $166, ops $27 of $31, presentation $27 of $31.

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

  3. Keep context lean$62

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

    60% of 1,575 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 Content Pipeline and the organization

PracticeBlakeTeamOrgTargetRecommendation
rtk coverage60%Needs attention62%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
29%Needs attention30%30%≥ 40% of sessionsSearch the knowledge MCP before re-researching a codebase, and save findings back with remember.
Cache hit rate77%Needs attention82%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 target9%10%≤ 10% of inputOn target
Opus on routine work88%Off target57%44%≤ 25% of routine spendDefault routine sessions to Sonnet and keep Opus for harness, design and hard debugging work.
Sessions using subagents53%On target55%50%≥ 30% of sessionsOn target
Tool error rate2.8%On target2.4%3.0%≤ 4% of tool callsOn target

Practices by month

Is the engineer moving toward the targets?

MonthrtkKnowledgeCacheContextModel fitSubagentsSavings opportunity
Feb 2026––57%Off target7%On target91%Off target31%On target$60
Mar 2026––64%Off target9%On target–42%On target$51
Apr 2026––69%Off target11%Needs attention91%Off target54%On target$65
May 202626%Off target–70%Needs attention9%On target90%Off target35%On target$77
Jun 202650%Needs attention12%Off target73%Needs attention7%On target90%Off target45%On target$127
Jul 202672%Needs attention25%Needs attention74%Needs attention6%On target88%Off target53%On target$106
Aug 202665%Needs attention33%Needs attention82%Needs attention7%On target88%Off target56%On target$55
Sep 202666%Needs attention38%Needs attention81%Needs attention10%On target86%Off target57%On target$82
Oct 202668%Needs attention34%Needs attention87%On target9%On target86%Off target71%On target$31
04

Usage

FY2027 to date

AI spend by model

By model tier, by month

  • Opus
  • Sonnet
  • Haiku
  • Other
$0$100$200$300$400$99Feb$136Mar$187Apr$179May$332Jun$249Jul$280Aug$351Sep$218Oct

AI spend by session type

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

Harness$579Freeform$695Code research$351Documentation$166Ideation$177Ops$31Presentation$31

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,03217M160.7M11.3M5.1M$259
Opus 54,60934.2M221M16.3M6.2M$539
Opus 4.83,20939.5M147.5M11.9M4.5M$459
Opus 4.63,74457.4M147.5M13.1M5.3M$576
Opus 4.51513.3M5.1M536K220K$28
Sonnet 5.54452.5M25.6M1.8M710K$19
Sonnet 59557.6M44.7M3.3M1.3M$69
Sonnet 4.65257.7M23M2M841K$50
Sonnet 4.531720K1.1M118K49K$4
Haiku 5.55782.5M28.8M2M729K$1
Haiku 4.55536.1M26.5M2.1M903K$16
GPT Realtime (meetings)1081.2M4.9M390K148K$11
Total17,940179.7M836.6M64.9M26.1M$2,030

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