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

Harper

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,104
211 sessions · $10 each
Savings opportunity
$587
28% of spend, at list price
Practices on target
3 of 7
Focus: Knowledge MCP use, rtk coverage
Cache hit rate
83%
Team 82% · org 82%
02

Where spend could go further

FY2027 to date · estimated at list price

Savings opportunity by lever

$587 of $2,104 spend

Improve prompt caching$368Right-size models$133Keep context lean$67Route commands through rtk$19

What to change

Largest saving first

  1. Improve prompt caching$368

    Cache hit rate 83% 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$133

    45% of routine spend ran on Opus: code research $145 of $303, documentation $78 of $196, ops $40 of $100, presentation $59 of $120.

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

  3. Keep context lean$67

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

    65% of 1,783 Bash calls ran through rtk; 2.7M 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 Social Publishing and the organization

PracticeHarperTeamOrgTargetRecommendation
rtk coverage65%Needs attention63%56%≥ 80% of Bash callsInstall the rtk hook so test, build, git and search commands return compact output.
Knowledge MCP use3%Off target4%30%≥ 40% of sessionsSearch the knowledge MCP before re-researching a codebase, and save findings back with remember.
Cache hit rate83%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 100K9%On target9%10%≤ 10% of inputOn target
Opus on routine work45%Needs attention44%44%≤ 25% of routine spendDefault routine sessions to Sonnet and keep Opus for harness, design and hard debugging work.
Sessions using subagents47%On target46%50%≥ 30% of sessionsOn target
Tool error rate3.2%On target3.7%3.0%≤ 4% of tool callsOn target

Practices by month

Is the engineer moving toward the targets?

MonthrtkKnowledgeCacheContextModel fitSubagentsSavings opportunity
Feb 2026––62%Off target11%Needs attention62%Off target43%On target$43
Mar 2026––67%Off target11%Needs attention62%Off target26%Needs attention$87
Apr 2026––66%Off target7%On target62%Off target38%On target$98
May 202624%Off target–67%Off target11%Needs attention55%Off target35%On target$101
Jun 202650%Needs attention3%Off target72%Needs attention6%On target53%Off target39%On target$61
Jul 202669%Needs attention3%Off target75%Needs attention8%On target40%Needs attention41%On target$70
Aug 202674%Needs attention4%Off target79%Needs attention11%Needs attention38%Needs attention54%On target$67
Sep 202668%Needs attention2%Off target83%Needs attention9%On target30%Needs attention44%On target$31
Oct 202676%Needs attention2%Off target91%On target9%On target27%Needs attention69%On target$30
04

Usage

FY2027 to date

AI spend by model

By model tier, by month

  • Opus
  • Sonnet
  • Haiku
  • Other
$0$200$400$600$88Feb$210Mar$213Apr$218May$162Jun$272Jul$309Aug$207Sep$424Oct

AI spend by session type

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

Harness$441Freeform$825Code research$303Documentation$196Ideation$120Ops$100Presentation$120

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,2176.6M171.9M11.4M5.4M$226
Opus 52,62320.1M119.8M8.9M3.8M$312
Opus 4.81,85821.5M78.2M6.4M2.7M$254
Opus 4.63,31554.1M130M11.7M5.1M$536
Opus 4.51122.3M4.6M440K161K$21
Sonnet 5.54,5099M270.5M17.8M7.5M$165
Sonnet 54,08730.5M187.2M13.9M5.9M$289
Sonnet 4.62,16133.6M88.6M7.8M3.1M$204
Sonnet 4.51102.1M4.1M395K155K$11
Haiku 5.58,19411.7M401.7M26.4M9.6M$13
Haiku 4.52,60025.7M118.5M9.2M3.7M$68
GPT Realtime (meetings)77634K4M298K116K$7
Total32,863217.9M1579.1M114.7M47.3M$2,104

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